pypi
AGENTS.md23 starsChanged 26 days agoApache-2.0View on GitHub
Tools that build and publish Sentry's internal PyPI index at https://pypi.devinfra.sentry.io/simple. packages.ini lists every package version the index serves.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- upgrade-pythonSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Add a package: python3 -m add_pkg PKGNAME
- Very specific: line 12
Add the newest PyPI release of every package: python3 -m upgrade_all
- Very specific: line 17
Put no # comments in packages.ini.
- Very specific: line 18
Every dependency of a package must also be in packages.ini, or validation fails.
- Distinctive: line 19
Never overwrite a published wheel.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
Tools that build and publish Sentry's internal PyPI index at https://pypi.devinfra.sentry.io/simple.
packages.ini lists every package version the index serves.
commands
- Set up:
uv sync, thendirenv allowto install the pre-commit hooks. - Test:
uv run coverage run -m pytest tests && uv run coverage report - Lint and format:
pre-commit run --files <changed files> - Add a package:
python3 -m add_pkg PKGNAME - Add the newest PyPI release of every package:
python3 -m upgrade_all - Format
packages.ini:python3 -m format_ini packages.ini
invariants
- Put no
#comments inpackages.ini.format_ini.pydrops them. - Every dependency of a package must also be in
packages.ini, or validation fails. - Never overwrite a published wheel. Deletion is a manual process for security cases.
PYTHONSinbuild.pyandvalidate.pyandVERSIONSindocker/install-pythonslist the same Python versions.
docs
| Topic | Doc |
| Use the index and add a package | README.md |
packages.ini options | docs/packages-ini.md |
| How CI builds, validates, and deploys | docs/build-pipeline.md |
| Delete a published package | docs/deleting-packages.md |
| Add a new Python version | upgrade-python skill |
| Python 3.14 upgrade failures (dated record) | PYTHON-3.14-UPGRADE.md |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.