On Tue, Jul 13, 2010 at 4:25 PM, Brett Cannon <brett at python.org> wrote: > Can I ask why you did this? 0 does not block import in py3k: >>> import sys >>> sys.modules['time'] = 0 >>> import time >>> time 0 I ran into this problem while working on datetime.py tests. I asked on python-dev and Nick said it was an oversight. http://mail.python.org/pipermail/python-dev/2010-July/101883.html > And just for historical background, the reason this was originally 0 instead > of None is that before absolute imports an entry in None was used to force > an absolute import instead of a relative import in a package. This doesn't > come into play in Python 3, though. I was not planning to backport to 2.x. Is there a problem with this change in 3.x?
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