[issue24468] Expose C level compiler flag constants to Python code

Larry Hastings added the comment: opcode.patch is okay for 3.5. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue24468] Expose C level compiler flag constants to Python code

Nick Coghlan added the comment: Making _opcode a builtin module rather than an extension module makes more sense to me than adding more random stuff to the sys module. -- ___ Python tracker ___

[issue24468] Expose C level compiler flag constants to Python code

Yury Selivanov added the comment: Larry, Nick, Attached patch exposes CO* constants in the '_opcode' module. There is one slight complication though: importing '_opcode' in 'types' (required for issue24400) breaks Python compilation, as 'types' module is used by many tools at the point where

[issue24468] Expose C level compiler flag constants to Python code

Nick Coghlan added the comment: Bringing a design discussion back from the code review, since I didn't explain the problem to be solved very well, and instead jumped straight to recommending a specific solution. Currently, dis has a dictionary mapping from hardcoded compiler flag values (in d