[Python-Dev] PEP 423 : naming conventions and recipes related to packaging

Yury Selivanov yselivanov.ml at gmail.com
Wed Jun 27 22:08:38 CEST 2012


On 2012-06-27, at 10:57 AM, Paul Moore wrote:

> Generally, the impression I get is that the PEP is recommending more
> levels of nesting than I would agree with: But it's hard to be sure,
> because the concept of nesting feels a bit overloaded. The key for me
> is that generally, I like to be able to type "import X" where X is not
> a dotted name, and then refer to X.x1, X.x2, etc. I'd call that no
> levels of nesting, to be honest. For complex stuff, subpackages
> ("import X.Y") might be needed, but that's rare (and even then, key
> names should be exposed directly from X).

Why instead of writing 'import project' you don't want to write
'from acme import project'?

With python adoption (enterprise too) growing, we will inevitably 
find out that one single namespace (PyPI) is not enough, and
name collisions will become a frequent headache.

-
Yury


More information about the Python-Dev mailing list