[Python-Dev] Release manager pronouncement needed: PEP 302 Fix (original) (raw)
Phillip J. Eby pje at telecommunity.com
Wed Jul 26 20:40:27 CEST 2006
- Previous message: [Python-Dev] New miniconf module
- Next message: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I posted last week about a need-for-speed patch that broke PEP 302 compliance, and asked if it should be fixed or reverted. I got exactly one response which said "yes, it should be fixed or reverted", which unfortunately didn't answer my question as to which one we should do. :)
If we don't revert it, there are two ways to fix it. One is to just change PEP 302 so that the behavior is unbroken by definition. :) The other is to actually go ahead and fix it by adding PathImporter and NullImporter types to import.c, along with a factory function on sys.path_hooks to create them. (This would've been the PEP-compliant way to implement the need-for-speed patch.)
So, "fix" by documentation, fix by fixing, or fix by reverting? Which should it be?
- Previous message: [Python-Dev] New miniconf module
- Next message: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]