[issue14169] compiler.compile fails on "if" statement in attached file

Terry J. Reedy added the comment: I agree. 'deprecated' pretty much means "We do not think this is worth the effort of maintaining it. Don't use it unless it is already in old code." -- resolution: -> wont fix status: open -> closed ___ Python trac

[issue14169] compiler.compile fails on "if" statement in attached file

Mark Dickinson added the comment: Okay, so the issue is simply that the compiler module doesn't have logic for emitting the EXTENDED_ARGS[1] bytecode instruction to properly deal with a jump target that won't fit in two bytes. Given that the compiler module is deprecated, I propose closing t

[issue14169] compiler.compile fails on "if" statement in attached file

Mark Dickinson added the comment: D'oh. Ignore that last message; all it shows is that I'm stupid. -- ___ Python tracker ___ ___ P

[issue14169] compiler.compile fails on "if" statement in attached file

Mark Dickinson added the comment: Interestingly, dis.dis also fails to decompile the .pyc bytecode generated by importing the file. (This was after adding dummy AddUnit, MakeCustomaryToBase and MakeBaseToCustomary definitions to the top of the file to prevent the import raising an exception.

[issue14169] compiler.compile fails on "if" statement in attached file

Mark Dickinson added the comment: Here's the trackback I get with Python 2.7. Look's like something's assuming that POP_JUMP_IF_FALSE target of 65541 fits in 16 bits. Python 2.7.2 (default, Jan 13 2012, 17:11:09) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright"

[issue14169] compiler.compile fails on "if" statement in attached file

Jim Jewett added the comment: If I understood correctly, that *is* the minimal case, which suggests some sort of size problem. That said, I could not duplicate on 2.6.2, nor with py_compile.compiler in 3.2.2; I am not currently sufficiently motivated to install another version just for this

[issue14169] compiler.compile fails on "if" statement in attached file

Changes by Meador Inge : -- nosy: +meador.inge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14169] compiler.compile fails on "if" statement in attached file

Changes by Antoine Pitrou : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue14169] compiler.compile fails on "if" statement in attached file

Terry J. Reedy added the comment: Please provide a *minimal* example that exhibits the problem. 'Minimal' means that if a single line is removed, the problem disappears. -- nosy: +terry.reedy ___ Python tracker _

[issue14169] compiler.compile fails on "if" statement in attached file

New submission from Fabio Menegazzo : compiler.compile fails on "if" statement in attached file. When executing the code compiler.compile(contents, '', 'exec') passing the attached file contents, the following error is raised: ValueError: chr() arg not in range(256) This won't fail w