Mailman 3 June 2012 - docs

[issue12982] Document that importing .pyo files needs python -O
by R. David Murray June 14, 2012

June 14, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: Because: 1) The __debug__ flag is defined to be process-global. If you test it in one module, your code should be able to assume that it has the same value in all other modules 2) python-dev does not support running .pyo code without -O turned on. In the future it might be the case that -O would actually change the behavior of the running python interpreter such that .pyo code would fail of -O was not on. So, you can do the rename or importer trick if you want, and it will work right now as long as your program does not depend on __debug__ being globally consistent (which would be the case for almost all programs), but we do not guarantee it will continue to work in future versions of Python. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] Document that importing .pyo files needs python -O
by Michael Herrmann June 14, 2012

June 14, 2012

Michael Herrmann <mherrmann.at(a)gmail.com> added the comment: That is *exactly* my point :) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] Document that importing .pyo files needs python -O
by Eric O. LEBIGOT June 14, 2012

June 14, 2012

Eric O. LEBIGOT <eric.lebigot(a)normalesup.org> added the comment: Terry, it seems that the doc I was quoting is for version 1.5.1 (http://docs.python.org/release/1.5.1p1/tut/node43.html). I can't find it in more recent versions of the doc. I should not have quoted an obsolete version of the documentation—I'm not sure how this happened. :) I am not fully sure why -O is essentially required for running .pyo files: why not have the Python interpreter handle everything automatically based on the extension? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] Document that importing .pyo files needs python -O
by Terry J. Reedy June 14, 2012

June 14, 2012

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: The response from pydev is that running .pyc with -O or running .pyo without is not officially supported. Even if mixing usually works now, it does not always work properly for code with __debug__, assert, or __doc__. The scope of possible malfunctions may increase if ideas for more aggressive optimization are implemented. So mixing the two types of cache files is 'do at your own risk' and 'don't complain if it does not work now or ceases to work in the future'. A principle reason for the above is that __debug__ == <not -O> and that it affects complilation, not just execution. The doc should say the above more clearly. Eric L., where is the doc quote from? ---------- components: +Documentation -Interpreter Core _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue15060] docs: socket typo
by anatoly techtonik June 13, 2012

June 13, 2012

New submission from anatoly techtonik <techtonik(a)gmail.com>: http://docs.python.org/library/socket.html s/integral/integer/ ---------- assignee: docs@python components: Documentation messages: 162720 nosy: docs@python, techtonik priority: normal severity: normal status: open title: docs: socket typo _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15060> _______________________________________

3 3

[issue12982] Document that importing .pyo files needs python -O
by Ronan Lamy June 12, 2012

June 12, 2012

Changes by Ronan Lamy <ronan.lamy(a)gmail.com>: ---------- nosy: +Ronan.Lamy _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] Document that importing .pyo files needs python -O
by Terry J. Reedy June 12, 2012

June 12, 2012

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: Michael, you should ask the closed source library distributor to distribute all files as .pyc so you have access to docstrings while programming and to avoid the problem with reading them. He could also distribute an all-.pyo version. A mixture seems accidental. Is the import restriction currently intended? If a change *is* made, should it be regarded as an enhancement rather than a bug fix? I asked both question on pydev for more input. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] Document that importing .pyo files needs python -O
by Michael Herrmann June 12, 2012

June 12, 2012

Michael Herrmann <mherrmann.at(a)gmail.com> added the comment: Dear Eric OL, I see - I had read your e-mail but because of the similar names I thought the message here was yours too, and thus only replied once. I apologize! I can of course find a workaround such as renaming .pyo to .pyc. However, I would like to avoid having to modify the distribution of the third party library I am using in any way. The reason is that if a new version of this third party library is released and I have to upgrade to this new version, I will again have to manually do all the changes I had to do for the old version for the new version, and of course some changes won't work any more and there will be problems... I'm finding it tedious to use the imp-module to read in the .pyo-files by hand and might just fall back to your suggestion. Thank you for it. Nevertheless, I am still hoping that this may be resolved in a future release. Best, Michael ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] Document that importing .pyo files needs python -O
by Michael Herrmann June 12, 2012

June 12, 2012

Michael Herrmann <mherrmann.at(a)gmail.com> added the comment: Hi Eric, thank you for your quick reply. I'm not the first one who encounters this problem and in my opinion it is simply counter-intuitive that you cannot read a mixture of .pyo and .pyc files. That is why I think that my proposed change is valuable. In the meantime, I will follow your suggestion and try to use the imp-module to load the .pyo-files myself. Thank you! Best regards, Michael ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

2 1

[issue12982] Document that importing .pyo files needs python -O
by R. David Murray June 12, 2012

June 12, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: Actually it's a lot easier than that, although it is very much a hack: just rename the .pyo files to .pyc, and python without -O will happily import them. Since the optimization happens when the bytecode is written, this does what you want. ---------- nosy: +r.david.murray _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0