Load a PEP 517 backend from within the source tree.
In PEP 517, package building backends are not loaded from the source of the package being built. This prevents accidentally shadowing your build system, but some packages, like build tools, want to act as their own backend.
intreehooks is a shim to work around this, so that a source tree can be built by itself. To use it, write a pyproject.toml like this:
[build-system]
requires = ["intreehooks"] # + any other packages required to build
build-backend = "intreehooks:loader"
[tool.intreehooks]
build-backend = "flit.buildapi" # Import path of your real backend
Metadata
Release files for intreehooks 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| intreehooks-1.0.tar.gz | 2.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| intreehooks-1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 6.4 kB
Release files / intreehooks-1.0.tar.gz
| Download URL | intreehooks-1.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87e600d3b16b97ed219c078681260639e77ef5a17c0e0dbdd5a302f99b4e34e1
|
|
BLAKE2b-256 checksum How to use checksums |
f9a55dacebf93232a847970921af2b020f9f2a8e0064e3a97727cd38efc77ba0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / intreehooks-1.0-py2.py3-none-any.whl
| Download URL | intreehooks-1.0-py2.py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
937fd547f6a8a913107eaba51875dd1e185c00c2f0e68bcb217821962db4caec
|
|
BLAKE2b-256 checksum How to use checksums |
725db6e188060e2a73b1d6eec7378ad18887c288a59a8cda1f5e2091519c91d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |