➜

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 petr.viktorin
Recipients James Salter, brett.cannon, ebfortin, eric.snow, larry, ncoghlan, paul.moore, petr.viktorin, steve.dower, tim.golden, zach.ware
Date 2015-09-04.10:10:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441361409.83.0.995920564146.issue24748@psf.upfronthosting.co.za>
In-reply-to
Content 
So, if I understand correctly, the problem is that the new imp.load_dynamic in 3.5.0b checks sys.modules, so if a module of the same name was loaded previously, it's only reloaded, skipping the create_module step.

This patch bypasses that check, so a new module is always loaded.

This brings this aspect of imp.load_dynamic to how it was in 3.4. However, I have no way to test if it fixes pywin32 or py2exe.
History
Date User Action Args
2015-09-04 10:10:09petr.viktorinsetrecipients: + petr.viktorin, brett.cannon, paul.moore, ncoghlan, larry, tim.golden, eric.snow, zach.ware, steve.dower, James Salter, ebfortin
2015-09-04 10:10:09petr.viktorinsetmessageid: <1441361409.83.0.995920564146.issue24748@psf.upfronthosting.co.za>
2015-09-04 10:10:09petr.viktorinlinkissue24748 messages
2015-09-04 10:10:09petr.viktorincreate