Skip to content

chore(python): ignore __pycache__ bytecode caches - #1015

Open
asdf80730 wants to merge 1 commit into
EasyIME:masterfrom
asdf80730:pr/gitignore-pycache
Open

asdf80730 wants to merge 1 commit into
EasyIME:masterfrom
asdf80730:pr/gitignore-pycache

Conversation

@asdf80730

Copy link
Copy Markdown
Contributor

__pycache__ directories appear next to the vendored Python sources as soon as anyone runs python -m compileall python or the unittest suite, and a broad git add then stages the .pyc files inside them — one local PR preparation committed 31 bytecode files before the mistake was caught. Ignoring the cache directory keeps bytecode out of the index.

Validation:

  • one-line .gitignore addition; no tracked path changes.

Fully generated by omp (Qwen3.8-Flash-Next) without human intervention.

__pycache__ directories appear next to the vendored Python sources as
soon as anyone runs compileall or the unittest suite, and a broad
`git add` then sweeps the .pyc files into a commit; one local PR
preparation carried 31 bytecode files before the mistake was caught.
Ignoring the cache directory keeps bytecode out of the index.

Fully generated by omp (Qwen3.8-Flash-Next) without human intervention.
asdf80730 added a commit to asdf80730/PIME that referenced this pull request Oct 27, 2026
The product .gitignore carries no __pycache__ entry until EasyIME#1015
lands, so a git add <dir> from a product worktree sweeps .pyc into the
commit and they ride the PR (happened on the EasyIME#844 branch before push). The
scope gate now FAILs any diff touching __pycache__/, pinned by a new
self-test assertion that force-adds a .pyc on a throwaway branch.

Fully generated by omp (Qwen3.8-Flash-Next) without human intervention.

This branch has not been deployed

No deployments
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