-
-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-85253: Exclude __pycache__
directories from backups using CACHEDIR.TAG
#21060
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…R.TAG This helps to prevent bloating backups with unwanted (possibly frequently changing, if __pycache__ directories are removed and recreated) files. Granted, one can add __pycache__ directory to their backup-tool-of-choice exclusion list, but those lists are ever growing and maybe it'd be good to help the tools and the users. See https://bford.info/cachedir/ for more information about the specification – it's supported by Borg, restic, GNU Tar and attic out of the box, other pieces of software (like rsync, Bacula and rdiff-backup) can be made to use it (partially, just the existence of the tag file is used, not its content)
merwok
reviewed
Jun 24, 2020
merwok
reviewed
Jun 24, 2020
Co-authored-by: Éric Araujo <[email protected]>
jstasiak
requested review from
brettcannon,
ericsnowcurrently,
ncoghlan and
warsaw
as code owners
December 15, 2023 17:52
brettcannon
changed the title
bpo-41081: Exclude __pycache__ directories from backups using CACHEDIR.TAG
gh-85253: Exclude Dec 18, 2023
__pycache__
directories from backups using CACHEDIR.TAG
FYI I don't think the issue for this has reached a conclusion that this is something we want to do yet. |
RazerM
reviewed
Jan 16, 2024
AA-Turner
reviewed
Jan 17, 2024
Co-authored-by: Frazer McLean <[email protected]>
Co-authored-by: Adam Turner <[email protected]>
Closing as I just closed the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This helps to prevent bloating backups with unwanted (possibly
frequently changing, if __pycache__ directories are removed and
recreated) files.
Granted, one can add __pycache__ directory to their
backup-tool-of-choice exclusion list, but those lists are ever
growing and maybe it'd be good to help the tools and the users.
See https://bford.info/cachedir/ for more information about the
specification – it's supported by Borg, restic, GNU Tar and attic
out of the box, other pieces of software (like rsync, Bacula and
rdiff-backup) can be made to use it (partially, just the existence of
the tag file is used, not its content)
https://bugs.python.org/issue41081