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 loewis
Recipients loewis, ned.deily, petri.lehtinen, python-dev, sbt, trent
Date 2012-08-31.14:57:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5040D0D0.10806@v.loewis.de>
In-reply-to <1346424038.29.0.327812760578.issue15819@psf.upfronthosting.co.za>
Content
Am 31.08.12 16:40, schrieb Richard Oudkerk:
> 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.

Why is that? python will work just fine if it can't write pyc files.

> 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.

Just for running setup.py? I don't see the need for that.
History
Date User Action Args
2012-08-31 14:57:22loewissetrecipients: + loewis, ned.deily, trent, python-dev, sbt, petri.lehtinen
2012-08-31 14:57:22loewislinkissue15819 messages
2012-08-31 14:57:21loewiscreate