RetroSearch Browse

Wed Apr 26 23:05:06 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-April/064436.html

At 01:49 PM 4/26/2006 -0700, Guido van Rossum wrote:
>OK, forget it. I'll face the pitchforks.
>
>I'm disappointed though -- it sounds like we can never change anything
>about Python any more because it will upset the oldtimers.

I know exactly how you feel.  :)

But there's always Python 3.0, and if we're refactoring the import 
machinery there, we can do this the right way, not just the "right now"
way.  ;)  IMO, if Py3K does this, it can and should be inclusive of 
top-level packages and assemble __path__ using all the sys.path 
entries.  If we're going to break it, let's break it all the way.  :)

I'm still really curious why the importer solution (especially if tucked 
away in a Google-defined sitecustomize) won't work, though.

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/064436.html below:

[Python-Dev] Dropping init.py requirement for subpackages

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/064436.html below:

[Python-Dev] Dropping __init__.py requirement for subpackages

[Python-Dev] Dropping init.py requirement for subpackages