pdm-pep517
A PEP 517 backend for PDM that supports PEP 621 metadata
Decision gist · record as of 2026-08-14
Yes, if you are building a Python project and want a modern, dependency-free PEP 517 backend. The package is production-stable, actively maintained, and has no runtime dependencies. Note: the project has been renamed to pdm-backend; verify whether that successor is recommended for new projects before committing to pdm-pep517.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.7 or later; the build frontend (e.g., python -m build) must be installed separately.
- Low friction installation with no runtime dependencies.
- Actively maintained as of 2026-08-03 with production-stable status.
License · maintenance · safety
MIT (permissive) — MIT license permits unrestricted use, modification, and distribution with minimal restrictions—suitable for any project type.
last release 2023-04-12 (1220 days) · last repo commit 2026-08-03 · 89 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 275,019 downloads/mo, #8,182 on PyPI
Alternatives
Verify before relying
# In pyproject.toml:
[build-system]
requires = ["pdm-pep517"]
build-backend = "pdm.pep517.api"
[project]
name = "mypackage"
dynamic = ["version"]
[tool.pdm.version]
source = "file"
path = "mypackage/__init__.py"
# Then build with: python -m build- Whether pdm-backend (the renamed successor) is recommended for new projects or if pdm-pep517 remains actively supported
- Performance characteristics when building large projects or those with complex custom build scripts
What it is and what it does
pdm-pep517 is a PEP 517-compliant build backend that integrates with Python's modern packaging standards. It reads project metadata from pyproject.toml in PEP 621 format and generates wheels and source distributions. The package supports dynamic version detection from static files or SCM tags (git/hg), custom build scripts for generating files at build time, and configuration options for controlling package layout, includes/excludes, and platform-specific wheel tags.
You use it by declaring it in your project's build-system section of pyproject.toml, then optionally configuring behavior under [tool.pdm.build]. It handles standard Python packaging workflows without requiring setuptools, though it can integrate with setuptools for C extension builds. The project is actively maintained and production-stable, supporting Python 3.7 through 3.11.
Use it for
- Build PDM projects or any project using PEP 621 metadata without setuptools or other legacy build tools
- Automatically detect and embed project version from git tags or SCM without hardcoding it in source
- Generate C extensions or other compiled artifacts during the build process via custom build scripts
- Create platform-specific wheels with custom tags for specialized deployment scenarios
- Manage complex package layouts with selective file inclusion/exclusion patterns
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building a Python project and want a modern, dependency-free PEP 517 backend.
The package is production-stable, actively maintained, and has no runtime dependencies. Note: the project has been renamed to pdm-backend; verify whether that successor is recommended for new projects before committing to pdm-pep517.
Install
pdm-pep517 on PyPI
Before you install
Low friction installation with no runtime dependencies. Actively maintained as of 2026-08-03 with production-stable status.
Requires Python 3.7 or later; the build frontend (e.g., python -m build) must be installed separately.
License in practice
MIT license permits unrestricted use, modification, and distribution with minimal restrictions—suitable for any project type.
Quickstart
# In pyproject.toml:
[build-system]
requires = ["pdm-pep517"]
build-backend = "pdm.pep517.api"
[project]
name = "mypackage"
dynamic = ["version"]
[tool.pdm.version]
source = "file"
path = "mypackage/__init__.py"
# Then build with: python -m buildVerify before relying
- Whether pdm-backend (the renamed successor) is recommended for new projects or if pdm-pep517 remains actively supported
- Performance characteristics when building large projects or those with complex custom build scripts
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.7 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 1,220 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 275,019 / month, #8,182 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9Topic :: Software Development :: Build Tools |
Evidence: pdm_pep517-1.1.4-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “dynamic version from SCM”
- pdm-pep517A PEP 517 build backend that reads PEP 621 project metadata from…
- setuptools-scm-git-archiveA setuptools_scm plugin that extracts version information from Git…
- vcvervcver generates version strings for Python packages by extracting…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also pdm-backend · whey · wheel-stub · build · pdm · flit-scm · pyproject-toml · pep517 · cmeel · pyproject-metadata