This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | benoitbryon |
|---|---|
| Recipients | benoitbryon, docs@python |
| Date | 2012年05月24日.12:42:05 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1337863326.85.0.0790625001968.issue14899@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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. Not covered by this issue. * Python has conventions about "syntax" of module names in PEP 8. Not covered by this issue. Goal: add guidelines+conventions about package names in Doc/packaging/ Discussion started at http://mail.python.org/pipermail/distutils-sig/2012-May/018551.html Jim Fulton said in http://mail.python.org/pipermail/distutils-sig/2012-May/018553.html: > +1 for an official document (or addition to an existinhg document) providing a rational for namespace packages and their naming Here is a ticket where proposals can be referenced. Contributions can be pushed on the "doc-package-naming-conventions" branch of https://bitbucket.org/benoitbryon/cpython |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年05月24日 12:42:06 | benoitbryon | set | recipients: + benoitbryon, docs@python |
| 2012年05月24日 12:42:06 | benoitbryon | set | messageid: <1337863326.85.0.0790625001968.issue14899@psf.upfronthosting.co.za> |
| 2012年05月24日 12:42:06 | benoitbryon | link | issue14899 messages |
| 2012年05月24日 12:42:05 | benoitbryon | create | |