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 | Jurko.Gospodnetić, barry, brett.cannon, eric.snow, ncoghlan, ned.deily, r.david.murray |
| Date | 2014年03月11日.11:02:34 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1394535754.5.0.244111694552.issue20884@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Reading https://bitbucket.org/anthony_tuininga/cx_freeze/src/default/cx_Freeze/finder.py I have a suspicion that the import system reimplementation in there is going to need updates to handle PEP 451 (I suspect there are even latent defects in relation to Python 3.3 changes). Setting this to pending for the moment - it needs someone that is more familiar than I am with cx-freeze internals to go over: The import related changes in http://docs.python.org/3/whatsnew/3.3.html#porting-to-python-3-3 The import related changes in http://docs.python.org/dev/whatsnew/3.4.html#changes-in-the-python-api The import system update in http://www.python.org/dev/peps/pep-0451/ In particular, issue 18065 (__path__ now being empty in frozen packages) seems like it might have the potential to cause trouble. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014年03月11日 11:02:34 | ncoghlan | set | recipients: + ncoghlan, barry, brett.cannon, ned.deily, r.david.murray, Jurko.Gospodnetić, eric.snow |
| 2014年03月11日 11:02:34 | ncoghlan | set | messageid: <1394535754.5.0.244111694552.issue20884@psf.upfronthosting.co.za> |
| 2014年03月11日 11:02:34 | ncoghlan | link | issue20884 messages |
| 2014年03月11日 11:02:34 | ncoghlan | create | |