{"owner":"python","repo":"typeshed","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# typeshed - Python type stub repository\n\ntypeshed contains [type stubs](https://typing.python.org/en/latest/spec/distributing.html)\nfor Python's standard library as well as for some packages available on\n[PyPI](https://pypi.org/) (usually called \"third-party stubs\" in typeshed)\nthat don't provide their own type annotations.\n\nThe standard library stubs get vendored by type checkers. Each third-party\nstub package is distributed as a separate package (usually called\n`types-<name>`) on PyPI.\n\n## Directory Structure\n\n- `stdlib/` - Python standard library stubs\n- `stubs/` - PyPI package stubs, one directory per package\n- `scripts`/ - utility scripts\n- `tests/` - scripts for various tests, see `tests/README.md`\n- `lib/` - utility modules used by multiple scripts\n\n## Running tests\n\nTo run all tests:\n\n- Create a new virtual environment (venv), update pip\n- Install the dependencies from `requirements-tests.txt` into it\n- Run `tests/runtests.py <path>` from the activated venv\n\n`<path>` is either:\n\n- `stdlib/<stub>.pyi`\n- `stubs/<package>`\n\nSee `tests/README.md` for more information about running tests.\n\n## Pull Requests\n\nWhen opening pull requests, do the following:\n\n- Follow the guidance from `CONTRIBUTING.md`.\n- Run the tests as described above before submitting.\n- Don't include tests for .pyi files, unless the situation is complex. See\n  `tests/REGRESSION.md`.\n- Use a concise PR description:\n  - Either link to an issue or describe the problem briefly, never both.\n  - Limit the summary of changes to one sentence, unless the PR is complex.\n  - Don't include a testing plan.\n- Add the name of the agent used to the PR description.\n"},"files":{"AGENTS.md":"# typeshed - Python type stub repository\n\ntypeshed contains [type stubs](https://typing.python.org/en/latest/spec/distributing.html)\nfor Python's standard library as well as for some packages available on\n[PyPI](https://pypi.org/) (usually called \"third-party stubs\" in typeshed)\nthat don't provide their own type annotations.\n\nThe standard library stubs get vendored by type checkers. Each third-party\nstub package is distributed as a separate package (usually called\n`types-<name>`) on PyPI.\n\n## Directory Structure\n\n- `stdlib/` - Python standard library stubs\n- `stubs/` - PyPI package stubs, one directory per package\n- `scripts`/ - utility scripts\n- `tests/` - scripts for various tests, see `tests/README.md`\n- `lib/` - utility modules used by multiple scripts\n\n## Running tests\n\nTo run all tests:\n\n- Create a new virtual environment (venv), update pip\n- Install the dependencies from `requirements-tests.txt` into it\n- Run `tests/runtests.py <path>` from the activated venv\n\n`<path>` is either:\n\n- `stdlib/<stub>.pyi`\n- `stubs/<package>`\n\nSee `tests/README.md` for more information about running tests.\n\n## Pull Requests\n\nWhen opening pull requests, do the following:\n\n- Follow the guidance from `CONTRIBUTING.md`.\n- Run the tests as described above before submitting.\n- Don't include tests for .pyi files, unless the situation is complex. See\n  `tests/REGRESSION.md`.\n- Use a concise PR description:\n  - Either link to an issue or describe the problem briefly, never both.\n  - Limit the summary of changes to one sentence, unless the PR is complex.\n  - Don't include a testing plan.\n- Add the name of the agent used to the PR description.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# typeshed - Python type stub repository\n\ntypeshed contains [type stubs](https://typing.python.org/en/latest/spec/distributing.html)\nfor Python's standard library as well as for some packages available on\n[PyPI](https://pypi.org/) (usually called \"third-party stubs\" in typeshed)\nthat don't provide their own type annotations.\n\nThe standard library stubs get vendored by type checkers. Each third-party\nstub package is distributed as a separate package (usually called\n`types-<name>`) on PyPI.\n\n## Directory Structure\n\n- `stdlib/` - Python standard library stubs\n- `stubs/` - PyPI package stubs, one directory per package\n- `scripts`/ - utility scripts\n- `tests/` - scripts for various tests, see `tests/README.md`\n- `lib/` - utility modules used by multiple scripts\n\n## Running tests\n\nTo run all tests:\n\n- Create a new virtual environment (venv), update pip\n- Install the dependencies from `requirements-tests.txt` into it\n- Run `tests/runtests.py <path>` from the activated venv\n\n`<path>` is either:\n\n- `stdlib/<stub>.pyi`\n- `stubs/<package>`\n\nSee `tests/README.md` for more information about running tests.\n\n## Pull Requests\n\nWhen opening pull requests, do the following:\n\n- Follow the guidance from `CONTRIBUTING.md`.\n- Run the tests as described above before submitting.\n- Don't include tests for .pyi files, unless the situation is complex. See\n  `tests/REGRESSION.md`.\n- Use a concise PR description:\n  - Either link to an issue or describe the problem briefly, never both.\n  - Limit the summary of changes to one sentence, unless the PR is complex.\n  - Don't include a testing plan.\n- Add the name of the agent used to the PR description.\n","category":"root","tokens":412}]}