Support for PEP 660 editable backend with different build-system
See original GitHub issue- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Feature Request
Currently poetry supports setup.py
or poetry based local package:
[tool.poetry.dependencies]
native = { path = "./native", develop = true }
However other build-systems are not supported (e.g. https://maturin.rs/develop.html#pep-660-editable-installs)
Issue Analytics
- State:
- Created a year ago
- Comments:20 (11 by maintainers)
Top Results From Across the Web
PEP 660 – Editable installs for pyproject.toml based builds ...
What to put in the wheel. Build backends must populate the generated wheel with files that when installed will result in an editable...
Read more >How to install a package using pip in editable mode with ...
Consider using a build backend that supports PEP 660. I'm using this inside a conda environment, the following is my version of setuptools...
Read more >pyproject.toml - pip documentation v22.3.1
For performing editable installs, pip will use PEP 660 build_wheel_for_editable hook that has to be provided by the build backend.
Read more >Build Configuration - PDM
A build backend is what drives the build system to build source distributions and ... PDM implements PEP 660 to build wheels for...
Read more >How we standardized editable installs PEP 660 vs ... - YouTube
A Python Enhancement Proposal ( PEP ) is the method through which the Python community debates and adopts new features to the language....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Is there an estimate of when the next version with the fix will be available? I’m stuck on this as well.
When “editable” is used, this works the same way as
pip install -e ./native
. Builds happen only according to what maturin does.If you update the code, the expectation is for you to run any build steps manually within the project. Alternatively, uninstall and reinstall: or update the package metadata.
This is because as far as poetry is concerned, if the metadata has not changed it needs to do nothing for the package.