New submission from Eric Snow: PJE brought up concerns on python-dev regarding PEP 451 and module reloading. [1] However, the issue isn't with the PEP changing reload semantics (mostly). Those actually changed with the switch to importlib (and a pure Python reload function) in the 3.3 release.
Nick sounded positive on fixing it, while Brett did not sound convinced it is worth it. I'm +1 as long as it isn't too complicated to fix. While we hash that out, here's a patch that hopefully demonstrates it isn't too complicated. :) [1] https://mail.python.org/pipermail/python-dev/2013-October/129863.html ---------- components: Library (Lib) files: reload-semantics.diff keywords: patch messages: 201407 nosy: brett.cannon, eric.snow, ncoghlan, pje priority: normal severity: normal stage: patch review status: open title: Reload semantics changed unexpectedly in Python 3.3 type: behavior versions: Python 3.3, Python 3.4 Added file: http://bugs.python.org/file32385/reload-semantics.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19413> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
