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 akaptur, barry, ezio.melotti, pconnell, r.david.murray
Date 2013-07-25.16:32:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well, the FAQ entry is "why didn't a .pyc file get created", so presumably the querant knows enough to be looking for one to get created, and so presumably knows more-or-less what it is.

It seems to me that your rewording loses the sense of answering the question, and instead becomes more of a mini-tutorial on what a .pyc file is.

The changes needed here, it seems to me, are to talk about the __pycache__ directory instead of the .pyc file.  In python2, the issue would be that there was no write access to the source directory, and thus the .pyc file could not be created.  Now that same lack of access will first of all result in the __pycache__ directory not being created.

There is also then a second level: if the __pycache__ directory already exists but is not writable when a new module is first run, the .pyc file will not get created.  But I bet almost no one will notice that, and thus it won't be a FAQ :)  

Still, that issue could be mentioned...but then you also need to mention the full, two-part, version-specific extension, since one has to know which .pyc file to expect, if there are multiple versions of python on the system.  That mention could just be a pointer to the relevant docs, though, since most users will only be dealing with one python3 version.
Date User Action Args
2013-07-25 16:32:53r.david.murraysetrecipients: + r.david.murray, barry, ezio.melotti, pconnell, akaptur
2013-07-25 16:32:53r.david.murraysetmessageid: <>
2013-07-25 16:32:53r.david.murraylinkissue18036 messages
2013-07-25 16:32:52r.david.murraycreate