Benoît Bryon ben...@marmelune.net added the comment:
The proposal has been added to PEPs repository as PEP 423 :
http://hg.python.org/peps/rev/52767ab7e140
Review is about to be started at python-...@python.org.
To adapt the scope of this issue, in cpython documentation, I am to:
* remove the
Changes by Alexis Metaireau ale...@notmyidea.org:
--
nosy: +alexis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14899
___
___
Python-bugs-list
Benoît Bryon ben...@marmelune.net added the comment:
I didn't provided the patch because the work is still at early stage. I planned
to provide a patch when the development branch is quite mature.
I created the issue early so that other people can contribute.
But I maybe I'd better read PEP 1
New submission from Benoît Bryon ben...@marmelune.net:
Scope:
* Python documentation lacks conventions, or at least guidelines,
to choose a name for a package.
* Python has tools to create and distribute packages.
Not covered by this issue.
* Python has tools to create namespace packages.
Benoît Bryon ben...@marmelune.net added the comment:
Use branch doc-package-names (not only conventions) instead.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14899
___
Benoît Bryon ben...@marmelune.net added the comment:
See Martin Aspeli's article at
http://www.martinaspeli.net/articles/the-naming-of-things-package-names-and-namespaces
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14899
Éric Araujo mer...@netwok.org added the comment:
Thanks for the report. You are confusing Python packages and the distributable
things that are also called packages (not by most of the distutils docs though
where they are named distributions). PEP 8 covers conventions for naming
modules
Changes by Éric Araujo mer...@netwok.org:
--
keywords: +patch
Added file: http://bugs.python.org/file25701/4b311ce6624b.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14899
___
