I recently acquired a new development laptop and moved a number of local Git repositories from my old machine to my new machine. In doing so I also changed the folder structure, and when trying to run some code I was presented with this Python error:<\/p>\n
This was a symptom of the fact that Python creates You can use the The command to find all If you want to delete all the files found, just add the Obviously, this can be used for any file type that you wish to eradicate, not just I don’t like having all of those extra files cluttering my machine, and, in addition to the error I mentioned above, I have from time to time seen other errors related to out of date Another issue that
\nimport file mismatch:
\nimported module 'tests.desktop.consumer_pages.test_details_page' has this __file__ attribute:
\n\/Users\/bsilverberg\/gitRepos\/marketplace-tests\/tests\/desktop\/consumer_pages\/test_details_page.py
\nwhich is not the same as the test file we want to collect:
\n\/Users\/bsilverberg\/Documents\/gitRepos\/marketplace-tests\/tests\/desktop\/consumer_pages\/test_details_page.py
\nHINT: remove __pycache__ \/ .pyc files and\/or use a unique basename for your test file modules
\n<\/code><\/p>\n.pyc<\/code> files on my machine when it compiles code. This can result in other nastiness too, as well as cluttering up your machine, so I wanted to both delete all of these files and also prevent Python from doing it in the future. This post contains info on how to do both.<\/p>\nDeleting all .pyc files from a folder<\/h3>\n
find<\/code> command (on OS X and Linux) to locate all of the .pyc<\/code> files, and then use its delete<\/code> option to delete them.<\/p>\n.pyc<\/code> files in all folders, starting with the current one is:
\nfind . -name '*.pyc'<\/code><\/p>\n-delete<\/code> option:
\nfind . -name '*.pyc' -delete<\/code><\/p>\n.pyc<\/code> files.<\/p>\nPreventing Python from writing .pyc files<\/h3>\n
.pyc<\/code> files.<\/p>\n.pyc<\/code> files can cause is that they can be orphaned, for example if you remove a .py<\/code> file from your project, but the .pyc<\/code> file remains (which can happen as one often adds *.pyc<\/code> to .gitignore<\/code>). Python can then still pick up the module from the .pyc<\/code> file via an import<\/code> which can lead to difficult to diagnose bugs.<\/p>\n