[Python-Dev] Release manager pronouncement needed: PEP 302 Fix

[Phillip J. Eby]

At 12:52 PM 7/27/2006 +0200, Georg Brandl wrote:
>Though beta1 and beta2 shipped with this change nobody reported any bug that
>could be linked to it

Actually, that's no longer true.  See:  http://python.org/sf/1529871

This is a user-reported bug against 2.5b2, and I have just confirmed that 
it is caused by the need-for-speed PEP 302 breakage.  Reverting r46372 
fixes the reported problem.

Of course, since I'm the author of the affected package, I can certainly 
fix the problem by updating my code.  (And in fact, setuptools 0.7a1 works 
because it uses 2.5's pkgutil when available, and r46372 included a fix for 
pkgutil.)

At this point, I'm going to wait another day for somebody to step up to fix 
the documentation, or the release manager to authorize inclusion of a 
proper fix (which is unlikely to be allowed, since it will mean adding two 
new types to import.c, and restructuring a bit of pkgutil to subclass from 
them).

(It's a nice performance improvement you've got here, I would hate to see 
anything happen to it...)

Personally, I would prefer to see it properly fixed in 2.5 rather than 
having to rip it out.  It's more work for me to create the proper fix than 
it is to just work around it in my code, but it seems a more righteous 
labor, if you know what I mean.  It also means that already-shipped and 
distributed versions of my code would work with the 2.5 release.