➜

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 ncoghlan
Recipients James Salter, brett.cannon, ebfortin, eric.snow, larry, ncoghlan, paul.moore, petr.viktorin, steve.dower, tim.golden, zach.ware
Date 2015-08-29.03:57:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440820650.25.0.201892322271.issue24748@psf.upfronthosting.co.za>
In-reply-to
Content 
Given that both pywin32 *and* py2exe have hit this, even if it can't be resolved for 3.5.0, it would be highly desirable to address it for 3.5.1.

It's certainly intended that load_module() keep working as it has previously, rather than forcing people to switch to exec_module() in order to support extensions modules properly on Windows. Aside from general backwards compatibility expectations, there are still some things that load_module() can do that the new PEP 451/489 mechanisms can't handle yet.
History
Date User Action Args
2015-08-29 03:57:30ncoghlansetrecipients: + ncoghlan, brett.cannon, paul.moore, larry, tim.golden, petr.viktorin, eric.snow, zach.ware, steve.dower, James Salter, ebfortin
2015-08-29 03:57:30ncoghlansetmessageid: <1440820650.25.0.201892322271.issue24748@psf.upfronthosting.co.za>
2015-08-29 03:57:30ncoghlanlinkissue24748 messages
2015-08-29 03:57:29ncoghlancreate