[issue21737] runpy.run_path() fails with frozen __main__ modules

2021-12-11 Thread Irit Katriel
Irit Katriel added the comment: The code looks very different from the patch now, is this issue still relevant? -- nosy: +iritkatriel status: open -> pending ___ Python tracker __

[issue21737] runpy.run_path() fails with frozen __main__ modules

2020-03-18 Thread Brett Cannon
Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue21737] runpy.run_path() fails with frozen __main__ modules

2014-06-12 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue21737] runpy.run_path() fails with frozen __main__ modules

2014-06-12 Thread Marc-Andre Lemburg
Changes by Marc-Andre Lemburg : -- keywords: +patch Added file: http://bugs.python.org/file35596/FrozenImporter-without-__main__-support.patch ___ Python tracker ___ ___

[issue21737] runpy.run_path() fails with frozen __main__ modules

2014-06-12 Thread Marc-Andre Lemburg
New submission from Marc-Andre Lemburg: The logic in runpy.run_path() assumes that removing the __main__ entry from sys.modules is enough to be able to use the module search logic for e.g. importing packages and ZIP files (with embedded __main__.py files). In Python 3.4 (and probably also 3.3