[issue2556] changing sys.dont_write_bytecode has not effect

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python

[issue2556] changing sys.dont_write_bytecode has not effect

Georg Brandl <[EMAIL PROTECTED]> added the comment: Sorry, I can't see what's wrong here. See import.c which indeed uses PySys_GetObject to retrieve the value of dont_write_bytecode. __ Tracker <[EMAIL PROTECTED]> ___

[issue2556] changing sys.dont_write_bytecode has not effect

New submission from Benjamin Peterson <[EMAIL PROTECTED]>: According to the 2.6 docs, says you can set it yourself to control bytecode generation. That doesn't work because the dont_write_bytecode flag is set from command option and never looked at again. Either we should remove this misleading i