➜

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 gvanrossum
Recipients brett.cannon, christian.heimes, doko, georg.brandl, gvanrossum, loewis, nnorwitz, skip.montanaro, thosrtanner
Date 2008-01-05.22:06:51
SpamBayes Score 0.0010190632
Marked as misclassified No
Message-id <1199570813.41.0.108987853278.issue602345@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm okay with this feature, and the patch looks fine, except I don't
like the names used.  It's not really about "read-only-ness" of
bytecode, it's about whether we write certain files.  I'd suggest naming
the envvar PYTHONDONTWRITEBYTECODE, the C flag variable
Py_DontWriteByteCodeFlag, and the sys variable sys.dont_write_byte_code.
 With those changes I'm find with Georg checkin it in.
History
Date User Action Args
2008-01-05 22:06:53gvanrossumsetspambayes_score: 0.00101906 -> 0.0010190632
recipients: + gvanrossum, loewis, skip.montanaro, nnorwitz, brett.cannon, georg.brandl, doko, christian.heimes, thosrtanner
2008-01-05 22:06:53gvanrossumsetspambayes_score: 0.00101906 -> 0.00101906
messageid: <1199570813.41.0.108987853278.issue602345@psf.upfronthosting.co.za>
2008-01-05 22:06:52gvanrossumlinkissue602345 messages
2008-01-05 22:06:51gvanrossumcreate