[issue1346572] Remove inconsistent behavior between import and zipimport

Changes by Éric Araujo : -- resolution: -> wont fix stage: needs patch -> committed/rejected status: open -> closed versions: -Python 2.7, Python 3.2, Python 3.3 ___ Python tracker _

[issue1346572] Remove inconsistent behavior between import and zipimport

Nick Coghlan added the comment: Status quo sounds fine then. +1 for closing it again. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue1346572] Remove inconsistent behavior between import and zipimport

Éric Araujo added the comment: > Does "compileall" generate both .pyc and .pyo by default? python3 -m compileall generates pyc, python3 -O -m compileall pyo. Functions in py_compile and compileall gained an optimize argument in 3.2. > does pysetup handle that for you? You’ll have to be more s

[issue1346572] Remove inconsistent behavior between import and zipimport

Nick Coghlan added the comment: Does "compileall" generate both .pyc and .pyo by default? Or do you have to run it twice? If the latter, does pysetup handle that for you? MvL is correct that zipimport should ignore .pyo files when __debug__ is set and vice-versa, but the precompilation tools

[issue1346572] Remove inconsistent behavior between import and zipimport

Éric Araujo added the comment: OK, I’m leaving this open until the next weekly report just in case someone interested comes here and weighs in, otherwise I’ll close as wontfix. -- ___ Python tracker ___

[issue1346572] Remove inconsistent behavior between import and zipimport

Brett Cannon added the comment: I don't care about compatibility between zipimport and importlib. -- ___ Python tracker ___ ___ Pyt

[issue1346572] Remove inconsistent behavior between import and zipimport

Éric Araujo added the comment: It entirely depends on how much you care about pyc-only/pyo-only zipfile distributions, and compatibility between zipimport and importlib (i.e. if you don’t plan on matching the zipimport bug in importlib, might as well fix zipimport in 2.7 and 3.2). --

[issue1346572] Remove inconsistent behavior between import and zipimport

Brett Cannon added the comment: I like that argument. =) If this is not an issue in Python 3.3 then this should be closed as out of date since it will break code if it is changed. -- ___ Python tracker

[issue1346572] Remove inconsistent behavior between import and zipimport

Éric Araujo added the comment: I need to qualify something: I reproduced the bug with legacy/pre-PEP 3147/in-the-same-dir pyc and pyo files. One could argue that pycache directories in 3.2+ make this irrelevant and that it’s too late for 2.x. -- _

[issue1346572] Remove inconsistent behavior between import and zipimport

Éric Araujo added the comment: Still an issue with 3.2: zipimport considers both pyc and pyo with or without -O. The discussion starts here: http://mail.python.org/pipermail/python-dev/2006-November/thread.html#69822 (This was originally closed instead of asking for another fix because Sour