#13362: bug8245 test fails on 1.1.X/Python2.3 after r12957
-------------------------------------------+--------------------------------
Reporter: kmtracey | Owner: brosner
Status: assigned | Milestone: 1.2
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by aaugustin):
This is actually documented in Python 2.4 release notes. Here is the
relevant excerpt of http://www.python.org/download/releases/2.4/notes/
When importing a module M raises an exception, Python no longer leaves M
in sys.modules. Before 2.4a2 it did, and a subsequent import of M would
succeed, picking up a module object from sys.modules reflecting as much of
the initialization of M as completed before the exception was raised.
Subsequent imports got no indication that M was in a partially-
initialized state, and the importers could get into arbitrarily bad
trouble as a result (the M they got was in an unintended state,
arbitrarily far removed from M's author's intent). Now subsequent imports
of M will continue raising exceptions (but if, for example, the source
code for M is edited between import attempts, then perhaps later attempts
will succeed, or raise a different exception).
So this is definitely a bug in Python 2.3. I do not know Django's policy
in such cases.
--
Ticket URL: <http://code.djangoproject.com/ticket/13362#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
