Yes, starting from Python 3.8 you can control this behavior. The original discussion starts from pep 304 in 2003. While this original PEP was withdrawn, a variant of this feature was eventually implemented for Python 3.8 in https://bugs.python.org/issue33499 In the result, you can control using PYTHONPYCACHEPREFIX=path, -X pycache_prefix=path and sys.pycache_prefix.
Remove .pyc files using git rm *.pyc. If this not work use git rm -f *.pyc Commit git commit -a -m ‘all pyc files removed’ Push git push In future commits you can ignore .pyc files by creating a .gitignore file
The .pyc files are created (and possibly overwritten) only when that python file is imported by some other script. If the import is called, Python checks to see if the .pyc file’s internal timestamp is not older than the corresponding .py file. If it is, it loads the .pyc; if it isn’t or if the … Read more
Tools to try Uncompyle6 works, with some bugs, for Python 3.x, and works well for 2.7. Recommended option to start with as it’s aiming to unify earlier forks and focusing on automated unit testing. The uncompyle6 GitHub page has more details. Works best for earlier 3.x versions, not best choice for 3.7+ If that doesn’t … Read more
.py: This is normally the input source code that you’ve written. .pyc: This is the compiled bytecode. If you import a module, python will build a *.pyc file that contains the bytecode to make importing it again later easier (and faster). .pyo: This was a file format used before Python 3.5 for *.pyc files that … Read more
I’ve been given to understand that Python is an interpreted language… This popular meme is incorrect, or, rather, constructed upon a misunderstanding of (natural) language levels: a similar mistake would be to say “the Bible is a hardcover book”. Let me explain that simile… “The Bible” is “a book” in the sense of being a … Read more