RetroSearch Browse

Wed Jun 27 13:19:57 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-June/120796.html

I thought the PEP actually covered it pretty well:
- if you don't want to worry about name conflicts for every module, pick
*one* short top level namespace for your group and use that
- for shared modules, use the top level namespace with PyPI as the name
registry

It's reasonable advice when coupled with the "avoid more than two levels of
nesting - when tempted by this, split out some peer modules" elsewhere in
the doc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120627/6974558c/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-June/120796.html below:

naming conventions and recipes related to packaging