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

Ned Deily report at bugs.python.org
Sat Nov 9 08:59:16 CET 2013


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 <directories from sys.path>.  Note the call in main() to compile_path vs those to compile_file or compile_dir.  I'm not sure if there was a good reason for the difference but it seems like a bug now.  Would you care to work on a patch and/or tests?

----------
keywords: +easy
nosy: +ned.deily
stage:  -> needs patch
versions: +Python 2.7, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19532>
_______________________________________


More information about the Python-bugs-list mailing list