[Python-Dev] Release manager pronouncement needed: PEP 302 Fix (original) (raw)
Phillip J. Eby pje at telecommunity.com
Fri Jul 28 17:30:31 CEST 2006
- Previous message: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix
- Next message: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 pathimportercache 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.
- Previous message: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix
- Next message: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]