PEP 517 and 518 are related and their combined changes are as follows.

A new standardized file named pyproject.toml will be read by pip for a section called [build-system] . This file specifies two things

  1. How to build a package (“wheel”) from source code (“sdist”) (PEP 517)

  2. Which packages need to be installed before trying to build. These are the build requirements. (PEP 518)

Here is an example of whatpyproject.toml looks like

requires = ["requests"]  # PEP 518 - what is required to build
build-backend = “tool.module:myfunction”  # PEP 517 - what function to call to build


This is a big deal because previously pip is literally hardcoded to run python to build packages when installing them from source. PEP 517 and 518 break that convention and let pyproject.toml tell pip how to build wheels and install them.

Most packages on PyPI are “wheels”, meaning they won’t be affected by this, but plenty still arent. Aditionally when you install from source code or a GitHub url you are installing from source.

Starting in pip version 19 when you run pip install on a folder with the abovepyproject.toml in it, pip will first install requests (per PEP 518) then callmyfunction() in ./tool/ (per PEP 517).

Below you can see what happens with a version of pip that does not have this change implemented. You can see that is hardcoded into pip!

> pip install -e .
Directory '.' is not installable. File '' not found.


pyproject.toml is allowed to have arbitrary fields in it so other tools can make use of it.

For example poetry adds project metadata like author and license in it, project dependencies, along with the PEP 517 and 518 fields for build system.

name = "myproject"
version = "0.1.0"
description = ""
authors = ["Chad Smith <[](>"]

python = "^3.7"
somepackage = "^0.13.1"

requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"


PEP 518 already landed in pip as of version 10. PEP 517 was implemented in pip in November 2018 (pull request, GitHub issue) and should be released in version 19 of pip in January 2019.

Some projects are already prepared for this when it occurs. For example when you runpoetry init , it’ll create a pyproject.toml file that’s compliant with PEP 518 and 517. [1]

requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"

This means when pip has PEP 517 implemented in it, you can install poetry-managed project directly from source code. For example pip install &lt;github url&gt; or pip install -e ..


Starting in version 19, pip will no longer be forced to use the hardcoded path to build installable packages from source code. More tools to build packages besides setuptools will be created and adopted in the ecosystem, such as poetry and flit.