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 ncoghlan
Recipients Steve.Thompson, amaury.forgeotdarc, barry, brian.curtin, desolat, eric.araujo, eric.snow, kevin.chen, markon, mucisland, ncoghlan, pdsimanyi, pitrou, python-dev
Date 2012-10-19.13:45:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350654354.52.0.155452289877.issue6074@psf.upfronthosting.co.za>
In-reply-to
Content
For 3.3+ I ended up using a tweaked version of Eric's patch - I kept the general test structure, but used the behavioural test I had created (i.e. does updating the initially read-only source file affect a subsequent bytecode only import?), as well as the simple rule of just always making the cached files writable by the owning user.

On 3.3+, this permissions tweak occurs regardless of OS, because I didn't think it was worth the runtime hit to make it OS specific (whereas the use of the C preprocessor previously made that not an issue).
History
Date User Action Args
2012-10-19 13:45:54ncoghlansetrecipients: + ncoghlan, barry, amaury.forgeotdarc, pitrou, eric.araujo, brian.curtin, pdsimanyi, markon, mucisland, Steve.Thompson, desolat, python-dev, eric.snow, kevin.chen
2012-10-19 13:45:54ncoghlansetmessageid: <1350654354.52.0.155452289877.issue6074@psf.upfronthosting.co.za>
2012-10-19 13:45:54ncoghlanlinkissue6074 messages
2012-10-19 13:45:54ncoghlancreate