[issue602345] option for not writing .py[co] files

[Tom Tanner]

Tom Tanner added the comment:

Is there likely to be any action on this. We can get issues with the
creation of .pyc files due to our build setup. We can get situations
where we run builds in parallel on 2 different architectures. Our build
is set up so that anything generated by compilers end up in individual
architecture specific directories, but we cannot do this with python. We
are also using clearmae, which has its own build avoidance features,
which get thoroughly confused by the generation of these files)

End result is one of
1) We get corrupt .pyc files
2) The build breaks
3) We rebuild things we don't need to.

We'd be very grateful for a way of suppressing the generation of .pyc
files completely.

----------
nosy: +thosrtanner

____________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue602345>
____________________________________