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 thosrtanner
Recipients brett.cannon, doko, georg.brandl, gvanrossum, loewis, nnorwitz, skip.montanaro, thosrtanner
Date 2007-10-19.10:01:01
SpamBayes Score 0.050053574
Marked as misclassified No
Message-id <1192788062.04.0.773243632085.issue602345@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2007-10-19 10:01:02thosrtannersetspambayes_score: 0.0500536 -> 0.050053574
recipients: + thosrtanner, gvanrossum, loewis, skip.montanaro, nnorwitz, brett.cannon, georg.brandl, doko
2007-10-19 10:01:02thosrtannersetspambayes_score: 0.0500536 -> 0.0500536
messageid: <1192788062.04.0.773243632085.issue602345@psf.upfronthosting.co.za>
2007-10-19 10:01:01thosrtannerlinkissue602345 messages
2007-10-19 10:01:01thosrtannercreate