https://github.com/takluyver/intreehooks

Load a PEP 517 backend from inside the source tree
https://github.com/takluyver/intreehooks

Last synced: about 2 months ago
JSON representation

Load a PEP 517 backend from inside the source tree

• Host: GitHub
• URL: https://github.com/takluyver/intreehooks
• Owner: takluyver
• License: mit
• Created: 2017-12-01T15:38:00.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2020-06-04T14:52:02.000Z (over 4 years ago)
• Last Synced: 2024-10-11T19:19:07.634Z (3 months ago)
• Language: Python
• Size: 7.81 KB
• Stars: 4
• Watchers: 4
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.rst
  • License: LICENSE

Awesome Lists containing this project

README

        
Load a PEP 517 backend from within the source tree.

This is **obsolete** now, because a ``backend-path`` key was added

to PEP 517, allowing it to `use in-tree backends natively

`_.

Before that, in `PEP 517 `_, package building

backends could not be 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:

.. code-block:: ini

    [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