pyproject.toml
A standardized configuration file for Python projects (PEP 518) used to declare the build system, project metadata, and dependency groups. It is widely supported by tools such as uv and pip.
Timeline (last 90 days)
The middleware has its own dependency group, and the official guidance requires adding the packages imported by the middleware to the vercel.proxy dependency group in pyproject.toml; the official toolkit can be installed via uv add --group vercel.proxy vercel-proxy.
PEP 735 introduced the dependency group standard feature for pyproject.toml, allowing dependencies to be divided into named groups under [dependency-groups] and installed group by group by tools such as uv.
Dependency provisioning belongs to the orchestration layer (requirements.txt, pyproject.toml, uv, Poetry, Dockerfile); the runtime should only consume an environment already in place and, when dependencies are missing, fail immediately with installation instructions.
Plugin developers should explicitly write every third-party module actually imported into the dependency declarations in pyproject.toml or setup.py.
In Python, the dependencies declaration in pyproject.toml determines the packages pulled in by pip at install time and the range of version constraints.
For teams still using requirements.txt, migrating to the Vercel Python runtime requires migrating dependencies to the pyproject.toml format, but the migration cost is low.
Vercel's Python runtime runs CPython on Linux, and dependency management supports uv and pyproject.toml.
uv is a package management and environment tool in the Python community, focused on extremely fast resolution and installation speed, using pyproject.toml as a unified project and dependency declaration file, and is gradually replacing the traditional combination of requirements.txt plus virtualenv.
The choice of build backend is written into a project's pyproject.toml and affects all users who install the package from source, thus turning from a personal preference into part of the project's external contract.
PEP 517 defines the build process and interface specification from source packages to wheels, introduces the role of the build backend, and requires projects to declare build-backend and requires in the [build-system] table of pyproject.toml, based on which installation tools invoke standard hooks such as build_wheel in an isolated environment.
2 more timeline events
All Facts (15)
pyproject.toml采用TOML（Tom's Obvious Minimal Language）格式
95%UnverifiedPEP 621（2021年）进一步规范了pyproject.toml中项目元数据的存储格式
90%Unverifiedpyproject.toml最早由PEP 518（2016年）引入，用于声明构建系统依赖
90%UnverifiedPEP 735 introduced the dependency group standard feature for pyproject.toml, allowing dependencies to be divided into named groups under [dependency-groups] and installed group by group by tools such as uv.
50%UnverifiedThe middleware has its own dependency group, and the official guidance requires adding the packages imported by the middleware to the vercel.proxy dependency group in pyproject.toml; the official toolkit can be installed via uv add --group vercel.proxy vercel-proxy.
50%UnverifiedDependency provisioning belongs to the orchestration layer (requirements.txt, pyproject.toml, uv, Poetry, Dockerfile); the runtime should only consume an environment already in place and, when dependencies are missing, fail immediately with installation instructions.
50%UnverifiedPlugin developers should explicitly write every third-party module actually imported into the dependency declarations in pyproject.toml or setup.py.
50%UnverifiedIn Python, the dependencies declaration in pyproject.toml determines the packages pulled in by pip at install time and the range of version constraints.
50%UnverifiedVercel's Python runtime runs CPython on Linux, and dependency management supports uv and pyproject.toml.
50%Unverifieduv is a package management and environment tool in the Python community, focused on extremely fast resolution and installation speed, using pyproject.toml as a unified project and dependency declaration file, and is gradually replacing the traditional combination of requirements.txt plus virtualenv.
50%UnverifiedFor teams still using requirements.txt, migrating to the Vercel Python runtime requires migrating dependencies to the pyproject.toml format, but the migration cost is low.
50%UnverifiedPEP 517 defines the build process and interface specification from source packages to wheels, introduces the role of the build backend, and requires projects to declare build-backend and requires in the [build-system] table of pyproject.toml, based on which installation tools invoke standard hooks such as build_wheel in an isolated environment.
50%UnverifiedThe choice of build backend is written into a project's pyproject.toml and affects all users who install the package from source, thus turning from a personal preference into part of the project's external contract.
50%UnverifiedWhen the package version declared in pyproject.toml drifts from the record in the lock file, it may cause inconsistent behavior between local and CI environments.
50%UnverifiedPython's src layout and the pyproject.toml tooling have gradually become community standards.
50%