RetroSearch Browse

Tue Aug 8 17:11:43 CEST 2006 · http://mail.python.org/pipermail/python-dev/2006-August/068050.html

On Fri, 28 Jul 2006 18:00:36 -0400, "Phillip J. Eby" <pje at telecommunity.com> wrote:
>At 10:55 PM 7/28/2006 +0200, Martin v. Löwis wrote:
>>Phillip J. Eby wrote:
>> > The issue is that a proper fix that caches existence requires adding new
>> > types to import.c and thus might appear to be more of a feature.  I was
>> > therefore reluctant to embark upon the work without some assurance that it
>> > wouldn't be rejected as adding a last-minute feature.
>>
>>So do you have a patch, or are going to write one?
>
>Yes, it's checked in as r50916.
>
>It ultimately turned out to be simpler than I thought; only one new type
>(imp.NullImporter) was required.
>

Is this going to be the final state of PEP 302 support in Python 2.5?  I
don't particularly care how this ends up, but I'd like to know what has
been decided on (PEP 302 doesn't seem to have been updated yet) so I can
fix Twisted's test suite (which cannot even be run with Python 2.5b3
right now).

Jean-Paul

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

Showing content from http://mail.python.org/pipermail/python-dev/2006-August/068050.html below:

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