Skip to content

chore: untrack __pycache__ and ignore it - #64

Open
mdheller wants to merge 1 commit into
mainfrom
chore/untrack-pycache
Open

chore: untrack __pycache__ and ignore it#64
mdheller wants to merge 1 commit into
mainfrom
chore/untrack-pycache

Conversation

@mdheller

@mdheller mdheller commented Aug 5, 2026

Copy link
Copy Markdown
Member

Four .pyc files were tracked in this repo. Three of them I committed in #62, by running git add -A in a worktree without checking what it swept up — in a change whose whole purpose was correcting a previous unverified fix.

They are build artefacts: no review value, churn on every Python version, and they had already caused a real problem earlier tonight when git checkout main here aborted because a tracked .pyc had local modifications.

Untracked, and .gitignore now covers __pycache__/, *.py[cod], *$py.class so it cannot recur.

No source change. 10 tests still pass.

Four .pyc files were tracked in this repo. THREE OF THEM I COMMITTED IN #62, by running
`git add -A` in a worktree without checking what it swept up — in a change whose entire purpose
was correcting a previous unverified fix.

They are build artefacts: they carry no review value, they churn on every Python version, and they
had already caused a concrete problem earlier tonight when `git checkout main` in this repo aborted
because a tracked .pyc had local modifications.

Untracked, and .gitignore now covers __pycache__/, *.py[cod] and *$py.class so it cannot recur.
No source change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant