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 sbt
Recipients loewis, ned.deily, petri.lehtinen, python-dev, sbt, trent
Date 2012-08-31.14:40:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Richard: what was your use case?

Building on the main host and a VM without having to commit and synchronize temporary changes.  (The VM has read-only access to the host's repositories).

> What steps did you take that resulted in getting and 
> written to?

As Martin says it is probably just the timestamps which caused to be rebuilt.  In 3.3 is rebuilt whenever the python binary is.

I suspect a bigger issue is the fact that *.pyc files cannot be written to $(srcdir)/Lib/__pycache__.  This means that to complete the build, $(PYTHON_FOR_BUILD) should probably include the -B flag to prevent it from trying to write *.pyc files to a read-only location.

But that still leaves you with a python which only works with the -B flag. Maybe library files could be linked/copied to some writable directory early in sys.path.
Date User Action Args
2012-08-31 14:40:38sbtsetrecipients: + sbt, loewis, ned.deily, trent, python-dev, petri.lehtinen
2012-08-31 14:40:38sbtsetmessageid: <>
2012-08-31 14:40:37sbtlinkissue15819 messages
2012-08-31 14:40:37sbtcreate