Example pyproject.toml configs for testing.
These are designed to be used in the testsuite for pyproject-parser and whey, but may be useful for other tools based on those.
Tests |
|
|---|---|
PyPI |
|
Activity |
|
QA |
|
Other |
|
Installation
pyproject-examples can be installed from PyPI.
To install with pip:
$ python -m pip install pyproject-examplesUsage
pyproject-examples provides the following API:
pyproject_examples module
valid_pep621_config
A list of pytest params for valid pyproject.toml files per PEP 621. The params contain the pyproject.toml content as a string. Each param has its own unique ID, which can be seen in the source here.
bad_pep621_config
A list of pytest params for invalid pyproject.toml files per PEP 621. Each param contains the pyproject.toml content (as a string), the expected Python exception (for catching with pytest.raises), and the expected exception text (for passing as the match argument to pytest.raises. Each param also has its own unique ID, which can be seen in the source here.
valid_buildsystem_config
A list of pytest params for valid [build-system] tables from pyproject.toml files per PEP 517 and PEP 517. The params contain the pyproject.toml content as a string. Each param has its own unique ID, which can be seen in the source here.
bad_buildsystem_config
A list of pytest params for invalid [build-system] tables from pyproject.toml files per PEP 517 and PEP 517. Each param contains the pyproject.toml content (as a string), the expected Python exception (for catching with pytest.raises), and the expected exception text (for passing as the match argument to pytest.raises. Each param also has its own unique ID, which can be seen in the source here.
pyproject_examples.example_configs submodule
This module contains the example configuration files themselves. Each file is stored as a string.
The configuration files are:
MINIMAL_CONFIG
KEYWORDS
AUTHORS
UNICODE
MAINTAINERS
CLASSIFIERS
DEPENDENCIES
OPTIONAL_DEPENDENCIES
OPTIONAL_DEPENDENCIES_EMPTY_GROUP
URLS
ENTRY_POINTS
COMPLETE_PROJECT_A
COMPLETE_A
COMPLETE_B
COMPLETE_A_WITH_FILES
DYNAMIC_REQUIREMENTS
LONG_REQUIREMENTS
pyproject_examples.utils submodule
This module contains utility functions.
file_not_found_regex(filename: str) -> str
This function create a regular expression for testing FileNotFoundErrors.
This is useful for testing error messages between Windows and POSIX, as well as between CPython and PyPy.
filename The filename which can’t be found.
1 maintainer
Metadata
1 maintainer
Release files for pyproject-examples 2026.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyproject_examples-2026.2.3.tar.gz | 7.2 kB | Without provenance | Details for pyproject_examples-2026.2.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyproject_examples-2026.2.3-py3-none-any.whl | Python 3 | none | any | Details for pyproject_examples-2026.2.3-py3-none-any.whl |
Total release size: 17.9 kB
Release files / pyproject_examples-2026.2.3.tar.gz
| Download URL | pyproject_examples-2026.2.3.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
953c1dd0e69922903674f2f634099279714da58bd695ebe36caa5ee98a3817f3
|
|
BLAKE2b-256 checksum How to use checksums |
553b7a5fb2c83c6b78251adc0165b1557ce4a20f91d10450bea37e6a4441c6f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / pyproject_examples-2026.2.3-py3-none-any.whl
| Download URL | pyproject_examples-2026.2.3-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2940f4f22212dc8756face2f47c7ff98a353a44faa99b99769c9ac201122807
|
|
BLAKE2b-256 checksum How to use checksums |
dba6111329dcfad69bdb280e80a819bcba0f40167fc0cd100e1d7108e81e5803
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for pyproject-examples 2026.2.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
