[Python-Dev] #12982: Should -O be required to read .pyo files? (original) (raw)

Toshio Kuratomi a.badger at gmail.com
Wed Jun 13 20:20:24 CEST 2012

On Wed, Jun 13, 2012 at 01:58:10PM -0400, R. David Murray wrote:

OK, but you didn't answer the question :). If I understand correctly, everything you said applies to writing the bytecode, not reading it. So, is there any reason to not use the .pyo file (if that's all that is around) when -O is not specified? The only technical reason I can see why -O should be required for a .pyo file to be used (if it is the only thing around) is if it won't run without the -O switch. Is there any expectation that that will ever be the case? Yes. For instance, if I create a .pyo with -OO it wouldn't have docstrings. Another piece of code can legally import that and try to use the docstring for something. This would fail if only the .pyo was present.

Of course, it would also fail under the present behaviour since no .py or .pyc was present to be imported. The error that's displayed might be clearer if we fail when attempting to read a .py/.pyc rather than failing when the docstring is found to be missing, though.

-Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20120613/6f43b067/attachment.pgp>

More information about the Python-Dev mailing list