Skip to content

chore: untrack 19 committed bytecode / egg-info files - #59

Open
CSOAI-ORG wants to merge 1 commit into
mainfrom
chore/untrack-bytecode-egginfo
Open

chore: untrack 19 committed bytecode / egg-info files#59
CSOAI-ORG wants to merge 1 commit into
mainfrom
chore/untrack-bytecode-egginfo

Conversation

@CSOAI-ORG

Copy link
Copy Markdown
Owner

19 build-output files were tracked in this repo:

  • SOVOS/packages/sovos-city/src/sovos_city/__pycache__/*.cpython-314.pyc β€” 9 files
  • SOVOS/packages/sovos.egg-info/* β€” 5 files
  • SOVOS/sovos.egg-info/* β€” 5 files

Tracked .pyc files are rewritten by the Python runtime as soon as anything imports those modules. Git then sees a dirty working tree and git pull refuses to fast-forward. That is exactly the failure that hit councilof-ai on 2026-09-02.

git rm --cached only β€” no file was deleted from disk.

.gitignore gains __pycache__/, *.py[cod] and *.egg-info/. The existing .DS_Store rule was already there and is untouched.

Not touched, deliberately

csoai.org/sovereign-os/dist/*.html and the dist/*.whl / dist/*.tar.gz artefacts elsewhere in the org look like intentionally committed build output (deployed pages, published packages), so I left them alone rather than guess.

πŸ€– Generated with Claude Code

9 .pyc files under SOVOS/packages/sovos-city and 10 .egg-info files under
SOVOS/packages/sovos.egg-info and SOVOS/sovos.egg-info were tracked. Tracked
bytecode is rewritten by the runtime, which makes an ordinary git pull fail to
fast-forward - the failure that hit councilof-ai on 2026-09-02.

git rm --cached only. No file was deleted from disk.

Signed-off-by: CSOAI-ORG <nicholas@csoai.org>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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