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
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.
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.
COBOL in its golden years had a practice th
* Ben Finney [110313 17:15]:
> Tim Johnson writes:
>
> > 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.
>
Tim Johnson writes:
> 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.
You'll never be able to make sure of that,
* David Marek [110311 13:20]:
> Hi,
>
> Have you read PEP 8? http://python.org/dev/peps/pep-0008/
> I don't think it's possible to be sure that the name of your module
> won't conflict with system module name (if you'll follow conventions).
>
> You can find the list of all PEPs at http://python.
Hi,
Have you read PEP 8? http://python.org/dev/peps/pep-0008/
I don't think it's possible to be sure that the name of your module
won't conflict with system module name (if you'll follow conventions).
You can find the list of all PEPs at http://python.org/dev/peps/
--
David Marek
dav...@atrey.k
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.
There may be a PEP for this, if so, a URL to such a PEP would
suffice f
On Mon, 14 Jan 2008 15:58:49 -0800 (PST), grackle <[EMAIL PROTECTED]> wrote:
> On Jan 14, 4:47 pm, Ben Finney <[EMAIL PROTECTED]>
> wrote:
>> I'm not sure, but it sounds as though you have yet to discover Python
>> module packages http://www.python.org/doc/essays/packages.html>.
>> They allow a hie
"Tobiah" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
|
| > Release your package as free software on the Cheeseshop
| > http://cheeseshop.python.org/>. If the name you want is already
| > taken, pick one that will help users distinguish yours from the
| > existing one.
| >
|
| I li
> Release your package as free software on the Cheeseshop
> http://cheeseshop.python.org/>. If the name you want is already
> taken, pick one that will help users distinguish yours from the
> existing one.
>
I like this idea. I developed a library with a name that got
a couple of obscure softwa
grackle <[EMAIL PROTECTED]> writes:
> On Jan 14, 6:28 pm, Ben Finney <[EMAIL PROTECTED]>
> wrote:
> > Release your package as free software on the Cheeseshop
> > http://cheeseshop.python.org/>. If the name you want is
> > already taken, pick one that will help users distinguish yours
> > from the
On Jan 14, 6:28 pm, Ben Finney <[EMAIL PROTECTED]>
wrote:
> grackle <[EMAIL PROTECTED]> writes:
> What do you mean by "top-level module", and "the same top-level name"?
> Do you mean "the same fully-qualified name"? If two modules are in
> separate places in the hierarchy, they will have different
On Jan 14, 11:44 am, grackle <[EMAIL PROTECTED]> wrote:
> Obviously Java-style naming is a mistake in Python, since top-level
> names have to be unique. Is there a standard naming convention to
> facilitate mixing code from different sources, such as
> mygroupname_modulename? Is there a best prac
grackle <[EMAIL PROTECTED]> writes:
> I do use packages. I mentioned the Java naming conventions because
> they were my first thought for solving the problem of name clashes,
> and they work well in some non-Java languages. They don't apply well
> to Python, since every top-level module has a uniq
On Jan 14, 4:47 pm, Ben Finney <[EMAIL PROTECTED]>
wrote:
> I'm not sure, but it sounds as though you have yet to discover Python
> module packages http://www.python.org/doc/essays/packages.html>.
> They allow a hierarchy of modules in directories.
I do use packages. I mentioned the Java naming c
grackle <[EMAIL PROTECTED]> writes:
> Obviously Java-style naming is a mistake in Python, since top-level
> names have to be unique. Is there a standard naming convention to
> facilitate mixing code from different sources, such as
> mygroupname_modulename? Is there a best practices guide for mod
Obviously Java-style naming is a mistake in Python, since top-level
names have to be unique. Is there a standard naming convention to
facilitate mixing code from different sources, such as
mygroupname_modulename? Is there a best practices guide for module
naming?
Thanks,
David
--
http://mail.py
18 matches
Mail list logo
