This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.snow
Recipients brett.cannon, eric.snow, ncoghlan, pje
Date 2013-11-01.17:52:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383328344.74.0.699907316394.issue19476@psf.upfronthosting.co.za>
In-reply-to
Content
In recent PEP 451-related discussions, the subject of reloading has come up multiple times.  Most recently, PJE suggested that reload semantics are under-specified (and under-tested). [1][2]

It may be worth adding a dedicated section on reloading to the reference doc.  As evidenced by that email thread (and issue #19413), there are some reload semantics that should be specified (and tested) but aren't.

While reload has a less prominent place in Python 3 (no longer a builtin), it is still a long-standing feature of the import system which gets used at more than just the interactive prompt.  I'd hate to see more issues like 19413 pop up later because of under-specification.  Furthermore, it would likely help other implementations pre-3.3 (a.k.a. pre-importlib) cover reload corner cases.

[1] https://mail.python.org/pipermail/python-dev/2013-October/129868.html
[2] https://mail.python.org/pipermail/python-dev/2013-October/129971.html
History
Date User Action Args
2013-11-01 17:52:24eric.snowsetrecipients: + eric.snow, brett.cannon, pje, ncoghlan
2013-11-01 17:52:24eric.snowsetmessageid: <1383328344.74.0.699907316394.issue19476@psf.upfronthosting.co.za>
2013-11-01 17:52:24eric.snowlinkissue19476 messages
2013-11-01 17:52:24eric.snowcreate