A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] Release manager pronouncement needed: PEP 302 Fix [Python-Dev] Release manager pronouncement needed: PEP 302 FixPhillip J. Eby pje at telecommunity.com
Fri Jul 28 17:30:31 CEST 2006
At 07:33 AM 7/28/2006 +0200, Martin v. Löwis wrote:
>Phillip J. Eby wrote:
> > I'm willing to write code that makes it PEP 302 compliant, if the release
> > manager will bless such an addition.  But if that's not acceptable, then
> > somebody needs to produce the necessary documentation updates or revert 
> the
> > patch.  It absolutely should not be allowed to remain in *and* 
> undocumented
> > because it is a backwards-incompatible change to documented behavior of
> > Python for two major releases (2.3 and 2.4).
>
>You don't need a release manager pronouncement for that. It's a bug,
>changing it is a bug fix, you don't need RM permission to fix a bug.
>
>Do you have a patch ready that restores path_importer_cache behavior,
>yet  preserves the property that it caches existence of a directory?
>If not, I will have to produce one.

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.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4