PEP for module naming conventions

[Jonathan Gossage]

I have found this approach problematic if you have packages separately
developed and maintained in different directory trees, resulting in
more than one PYTHONPATH entry with the same root metapackage name.
What happens is that only the first entry in the PYTHONPATH containing
the metapackage name is looked in for package/module resolution. Do
you have any suggestions for handling this kind of packaging?


On Thu, Mar 17, 2011 at 12:17 PM, eryksun () <eryksun at gmail.com> wrote:
> On Friday, March 11, 2011 4:52:57 PM UTC-5, Tim Johnson wrote:
>> I need to be better informed on naming conventions for modules.  For
>> instance, I need to create a new module and I want to make sure that
>> the module name will not conflict with any future or current python
>> system module names.
>
> Do you mean package names? Within a package you can use relative imports to avoid conflicts. You could put all of your packages in a metapackage namespace with a unique name -- a company/group name or personal/family name, an uncommon English word, or something from another language.
> --
> http://mail.python.org/mailman/listinfo/python-list
>