[Python-Dev] PEP 364, Transitioning to the Py3K standard library (original) (raw)
BJörn Lindqvist bjourne at gmail.com
Wed Mar 7 23:46:55 CET 2007
- Previous message: [Python-Dev] PEP 364, Transitioning to the Py3K standard library
- Next message: [Python-Dev] PEP 364, Transitioning to the Py3K standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
When Python's import machinery is initialized, the oldlib package is imported. Inside oldlib there is a class called
OldStdlibLoader
. This class implements the PEP 302 interface and is automatically instantiated, with zero arguments. The constructor reads all the.mv
files from the oldlib package directory, automatically registering all the remappings found in those.mv
files. This is how the Python 2.x standard library is remapped.
Will not reading all those .mv files add a lot of overhead? Disk seeks is not cheap.
-- mvh Björn
- Previous message: [Python-Dev] PEP 364, Transitioning to the Py3K standard library
- Next message: [Python-Dev] PEP 364, Transitioning to the Py3K standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]