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 r.david.murray
Recipients doko, ezio.melotti, michael.foord, r.david.murray, terry.reedy
Date 2015-09-19.18:45:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442688303.32.0.767621461553.issue21264@psf.upfronthosting.co.za>
In-reply-to
Content
Yes the point is to test compilation of the path.  If I run python3 -m compilelall on my installed python, it works fine (zero return code).  I can't really investigate this further right now, but it isn't obvious to me what the answer is from the information in the issue so far, except that it doesn't *look* like it should be necessary to skip the tests unless the installation directories are read only *and* the .pyc files in them are non-existent or out of date.
History
Date User Action Args
2015-09-19 18:45:03r.david.murraysetrecipients: + r.david.murray, terry.reedy, doko, ezio.melotti, michael.foord
2015-09-19 18:45:03r.david.murraysetmessageid: <1442688303.32.0.767621461553.issue21264@psf.upfronthosting.co.za>
2015-09-19 18:45:03r.david.murraylinkissue21264 messages
2015-09-19 18:45:03r.david.murraycreate