[issue1538778] pyo's are not overwritten by different optimization levels

Barry A. Warsaw added the comment: Thanks Toshio, I get it now. I think pre-generating the proper pyo's is probably the best solution. -- ___ Python tracker ___

[issue1538778] pyo's are not overwritten by different optimization levels

Toshio Kuratomi added the comment: It doesn't fix the problem as it falls into the third class of solutions (one that requires cooperation by the system administrator to diagnose and fix). OTOH, at this point in time I'm putting all of my packages in system packages where the .pyos are pregen

[issue1538778] pyo's are not overwritten by different optimization levels

Barry A. Warsaw added the comment: Uh, duh. Thanks for reminding me about that Arfrever! :) That should be everything Toshio needs I think. Plus this request is 4 years old. Closing as won't fix. -- resolution: -> wont fix status: open -> closed __

[issue1538778] pyo's are not overwritten by different optimization levels

Arfrever Frehtes Taifersar Arahesis added the comment: compileall module supports -f (force) option, so you can use: python3.2 -O -m compileall -f ${files} -- nosy: +Arfrever ___ Python tracker _

[issue1538778] pyo's are not overwritten by different optimization levels

Toshio Kuratomi added the comment: Here's a usage where this matters. It's a simplification of the bug report that I got that prompted me to open this. Let's say I have the following code: /usr/lib/python2.7/site-packages/foo.py:: def help(): """I'm a little docstring, short and

[issue1538778] pyo's are not overwritten by different optimization levels

Barry A. Warsaw added the comment: How is this different than overwriting pyc files, except that there's probably less of a use case for pycs? IOW, if we were to do something about this, it should probably be an option to ignore any existing pyc (or pyo if -O is used) files and write new one

[issue1538778] pyo's are not overwritten by different optimization levels

Changes by Éric Araujo : -- nosy: +barry, eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue1538778] pyo's are not overwritten by different optimization levels

Changes by Mark Lawrence : -- versions: +Python 3.2 -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue1538778] pyo's are not overwritten by different optimization levels

Changes by Brett Cannon : -- assignee: brett.cannon -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue1538778] pyo's are not overwritten by different optimization levels

Daniel Diniz added the comment: Confirmed in trunk. -- nosy: +ajaksu2 stage: -> test needed versions: +Python 2.7 ___ Python tracker ___ _

[issue1538778] pyo's are not overwritten by different optimization levels

Changes by Daniel Diniz : -- assignee: -> brett.cannon nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list