Albert-Jan Roskam writes:
> I know what it does
> (http://docs.python.org/2/using/cmdline.html#envvar-PYTHONDONTWRITEBYTECODE),
> i.e. no pyc or pyo fiules are written, but WHY is that sometimes a
> good thing?
There are numerous reasons why one might not want files to suddenly be
written when a
On Tue, Jan 21, 2014 at 2:44 PM, Albert-Jan Roskam wrote:
>
> Hmmm, number of OS * number of Python versions = a lot of packages. Isn't
> a .zip file easiest? Or maybe msi or wininst*) on Windows and .deb on
> Linux (with alien that can easily be converted to e.g. rpm).
The egg format is old and
>On Mon, Jan 20, 2014 at 5:42 AM, Albert-Jan Roskam wrote:
>>
>> When is setting a PYTHONDONTWRITEBYTECODE environment variable useful? Or
>> set sys.dont_write_bytecode to True? Or start Python with the -B option?
>> I know what it does
>> (http://docs.python.org/2/using/cmdline.html#envvar-PYT
On Mon, Jan 20, 2014 at 5:42 AM, Albert-Jan Roskam wrote:
>
> When is setting a PYTHONDONTWRITEBYTECODE environment variable useful? Or
> set sys.dont_write_bytecode to True? Or start Python with the -B option?
> I know what it does
> (http://docs.python.org/2/using/cmdline.html#envvar-PYTHONDONTW
On Mon, Jan 20, 2014 at 02:42:57AM -0800, Albert-Jan Roskam wrote:
> Hi,
>
>
> When is setting a PYTHONDONTWRITEBYTECODE environment variable useful? Or set
> sys.dont_write_bytecode to True? Or start Python with the -B option?
> I know what it does
> (http://docs.python.org/2/using/cmdline.htm
Hi,
When is setting a PYTHONDONTWRITEBYTECODE environment variable useful? Or set
sys.dont_write_bytecode to True? Or start Python with the -B option?
I know what it does
(http://docs.python.org/2/using/cmdline.html#envvar-PYTHONDONTWRITEBYTECODE),
i.e. no pyc or pyo fiules are written, but WH
