Purge __pycache__ from packages #1907
Assignees
Comments
legoktm
added a commit
that referenced
this issue
Mar 13, 2024
We already delete the individual .pyc files because they're not reproducible, but leave behind empty `__pycache__` folders. This can be annoying if people are doing builds out of a development checkout that has these folders that won't be present on a pristine build. So remove the empty folders right after deleting the .pyc files. Fixes #1907.
14 tasks
legoktm
added a commit
that referenced
this issue
Mar 14, 2024
We already delete the individual .pyc files because they're not reproducible, but leave behind empty `__pycache__` folders. This can be annoying if people are doing builds out of a development checkout that has these folders that won't be present on a pristine build. So remove the empty folders right after deleting the .pyc files. Fixes #1907. (cherry picked from commit 06ae37e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We had a bit of a mixup freedomofpress/securedrop-apt-test#218 at where people built in non-pristine checkouts, causing
__pycache__folders to get pulled in the packages. We should make sure these are never included, regardless if they exist on disk.The text was updated successfully, but these errors were encountered: