Remove tracked Python bytecode - #3
Draft
SWORDIntel wants to merge 1 commit into
Draft
Conversation
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.
What changed
__pycache__directories throughout the repository.Why
The existing ignore rules only covered root-level and SDK cache directories, allowing interpreter-specific generated files under
python/to remain tracked and recur.Impact
Source checkouts no longer carry stale interpreter bytecode, and normal Python execution will not dirty these paths again.
Validation
git diff --cached --checkgit check-ignorefor package and test cache pathsNo runtime tests were required because the change removes generated bytecode without modifying Python source.