[Python-Dev] [Python-checkins] r43033 - in python/trunk/Lib: distutils/sysconfig.py encodings/__init__.py
Thomas Wouters
thomas at python.org
Wed Mar 15 19:14:47 CET 2006
More information about the Python-Dev mailing list
Wed Mar 15 19:14:47 CET 2006
- Previous message: [Python-Dev] PEP 338 implemented in SVN
- Next message: [Python-Dev] [Python-checkins] r43033 - in python/trunk/Lib: distutils/sysconfig.py encodings/__init__.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/15/06, guido.van.rossum <python-checkins at python.org> wrote: > > > Use relative imports in a few places where I noticed the need. > (Ideally, all packages in Python 2.5 will use the relative import > syntax for all their relative import needs.) You should be aware that using relative imports (or absolute imports) in the standard library may cause custom __import__'s that don't take the optional fifth argument to break, whereas using 'old-style' imports does not. I don't know how common custom __import__ hooks are, and adding the optional fifth argument is backwardly compatible, but I would personally not add absolute or relative imports to the oft-used parts of the stdlib until after 2.5. On the other hand, code using sys.path_hooks (like zipimport) don't need any tweaking, as the absolute/relative choice is made before they are queried, so I don't know howmuch impact this has, all in all. -- Thomas Wouters <thomas at python.org> Hi! I'm a .signature virus! copy me into your .signature file to help me spread! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060315/6c0220cc/attachment.html
- Previous message: [Python-Dev] PEP 338 implemented in SVN
- Next message: [Python-Dev] [Python-checkins] r43033 - in python/trunk/Lib: distutils/sysconfig.py encodings/__init__.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list