chore: untrack compiled bytecode - #20
Merged
Merged
Conversation
194 .pyc files are tracked. .gitignore already lists __pycache__/ and *.pyc,
but .gitignore has no effect on files that are already tracked, so the rule
was added after these were committed and has been doing nothing for them
since.
Running the suite once rewrites them, so the working tree is dirty
immediately after any normal action:
$ pytest -q
1648 passed
$ git status --porcelain | wc -l
180
180 modified files, none of them source. Every contributor sees this on a
clean checkout the moment they run the tests. It makes git status useless
for its purpose, and a real edit sitting among 180 bytecode changes is easy
to miss — including on the way into a commit, where git add -A sweeps the
lot in.
The tracked bytecode is cpython-312 and this machine runs 3.14, so it is
regenerated rather than reused. It was not serving as a cache for anyone.
No other Python repository in the organisation tracks any: EoStudio, ebuild,
eDB and eApps are all at zero.
git rm --cached only. Nothing leaves the disk — 440 .pyc files are still
there and still regenerate on import — and no source file is touched:
staged removals 194
non-pyc among them 0
Suite unchanged at 1648 passed, 0 failed.
Closes #19
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #19.
194
.pycfiles are tracked..gitignorealready lists__pycache__/and*.pyc, but it has no effect on files that are already tracked — the rule wasadded after these were committed and has been doing nothing for them since.
Running the suite once rewrites them, so the working tree is dirty immediately
after any normal action:
180 modified files, none of them source. Every contributor sees this on a clean
checkout the moment they run the tests. It makes
git statususeless for itspurpose, and a real edit sitting among 180 bytecode changes is easy to miss —
including on the way into a commit, where
git add -Asweeps the lot in.The tracked bytecode is
cpython-312; this machine runs 3.14, so it isregenerated rather than reused. It was not serving as a cache for anyone.
No other Python repository in the organisation tracks any — EoStudio, ebuild,
eDB and eApps are all at zero.
Verified
git rm --cachedonly. Nothing leaves the disk, and no source file is touched:Suite unchanged: 1648 passed, 0 failed before and after.
Branches from
masterand is independent of #16 and #18, so it can merge in anyorder relative to them.