[issue19532] compileall -f doesn't force to write bytecode files

R. David Murray added the comment: Thanks, Vajrasky. I did not backport this to 2.7 because the code is different and we don't have proper tests there, so the chance of breaking something is higher than the benefit of fixing it. -- resolution: -> fixed stage: needs patch -> committed

[issue19532] compileall -f doesn't force to write bytecode files

Roundup Robot added the comment: New changeset 6afad4f29249 by R David Murray in branch '3.3': #19532: make compileall with no file/dir args respect -f and -q. http://hg.python.org/cpython/rev/6afad4f29249 New changeset 0e07ab605e0b by R David Murray in branch 'default': Merge: #19532: make comp

[issue19532] compileall -f doesn't force to write bytecode files

Vajrasky Kok added the comment: Tidied up the test. -- Added file: http://bugs.python.org/file32560/compileall_force_v3.patch ___ Python tracker ___ _

[issue19532] compileall -f doesn't force to write bytecode files

Vajrasky Kok added the comment: Ah, I missed that. I made this assumption because when I executed other modules manually, they were there just for testing functionality (such as shlex and aifc). Added test. -- Added file: http://bugs.python.org/file32559/compileall_force_v2.patch ___

[issue19532] compileall -f doesn't force to write bytecode files

R. David Murray added the comment: test_compileall has fairly extensive tests of the command line behavior, added when we refactored from optparse to argparse. So a test should be added for this case. -- nosy: +r.david.murray ___ Python tracker

[issue19532] compileall -f doesn't force to write bytecode files

Vajrasky Kok added the comment: Attached the patch to fix the problem. I did not modify the unit test because the bug was located in the __main__ part of Lib/compileall. -- keywords: +patch nosy: +vajrasky Added file: http://bugs.python.org/file32553/compileall_force.patch

[issue19532] compileall -f doesn't force to write bytecode files

Ned Deily added the comment: Looking at the compileall module, it appears that -f and options other than -b have never (or, at least, for a long time, not) been supported when directories or files are not supplied and it defaults to . Note the call in main() to compile_path vs those to compil

[issue19532] compileall -f doesn't force to write bytecode files

New submission from Sworddragon: The force-option from compileall seems not to rebuild the bytecode files if they already exist. Here is an example of 2 calls: root@ubuntu:~# python3 -m compileall -f Skipping current directory Listing '/usr/lib/python3.3'... Compiling '/usr/lib/python3.3/__phel