[Python-Dev] pycache creation (original) (raw)

"Martin v. Löwis" martin at v.loewis.de
Mon Mar 22 23🔞02 CET 2010

Why is it too late? Fix it, and get on. Sure, but it is annoying, and since it's the kind of things that noone (including sysadmins) ever thinks about in advance, it's bound to repeat itself quite often. It's especially annoying, of course, if you have to ask someone else to remove the directories for you (or if you have to write custom code and get it executed by the Apache or WSGI handler...). Really, it's unfriendly to users and it's certainly not outweighed by the "benefit" of having "cleaner" source directories.

Whether it is outweighed would also depend on how likely and frequent the presumed problem is, no?

If Apache creates a folder for me that I cannot remove, most likely, there was a configuration error in the first place: common practice tells that you should execute user code under user permissions, not as www-data. If your code does get run as Apache, this also opens a way of not asking for help: just put "os.system('chmod +w /.../pycache')" into your code, and have Apache run it again.

So I don't think this is any more unfriendly than creating .pyc files in the first place, and the advantages of uniformity of this new approach certainly outweigh the disadvantages.

Regards, Martin

More information about the Python-Dev mailing list