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 brett.cannon
Recipients brett.cannon, r.david.murray
Date 2009-08-31.00:37:09
SpamBayes Score 6.2730154e-11
Marked as misclassified No
Message-id <1251679032.24.0.484990647778.issue6526@psf.upfronthosting.co.za>
In-reply-to
Content
Turns out the failure is because I have simply been opening bytecode 
files for writing using _io.FileIO(..., 'w') which just uses the OS's 
default permissions. Guess that won't cut it anymore. =)

So does this mean I am expected to chmod the bytecode file to have 
matching read and write bits to the source but no execution bits 
regardless of the source file? And what about writing new bytecode 
files? I am not about to ignore permissions and simply write over files 
just because I can as someone could have set them independently of 
Python to be read-only.

Let me know that I am doing the right thing, David.
History
Date User Action Args
2009-08-31 00:37:12brett.cannonsetrecipients: + brett.cannon, r.david.murray
2009-08-31 00:37:12brett.cannonsetmessageid: <1251679032.24.0.484990647778.issue6526@psf.upfronthosting.co.za>
2009-08-31 00:37:10brett.cannonlinkissue6526 messages
2009-08-31 00:37:09brett.cannoncreate