This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients Arfrever, alexis, eric.araujo, tarek
Date 2011-11-26.13:40:16
SpamBayes Score 0.0012345887
Marked as misclassified No
Message-id <1322314817.65.0.411534925853.issue13400@psf.upfronthosting.co.za>
In-reply-to
Content
Okay, I think it’s a valuable use case.

(Out of curiosity, why don’t you want byte-compiled files on your system?  It speeds up imports, and problems due to the presence of stray pyc files when the py is deleted are gone in 3.2+.  Maybe you have custom tools to byte-compile, like Debian?)

Do you have any opinion about my renaming suggestion?
Without renaming, we’d have that:

  build --byte-compile --no-byte-compile --optimize-bytecode=[012]
  build_py --compile --no-compile --optimize=[012]

If we want to use the same name and make the names clearer, we could have:

  build(_py) --compile-pyc --no-compile-pyc --compile-pyo=[012]
History
Date User Action Args
2011-11-26 13:40:17eric.araujosetrecipients: + eric.araujo, tarek, Arfrever, alexis
2011-11-26 13:40:17eric.araujosetmessageid: <1322314817.65.0.411534925853.issue13400@psf.upfronthosting.co.za>
2011-11-26 13:40:17eric.araujolinkissue13400 messages
2011-11-26 13:40:16eric.araujocreate