PEP 660 standardises the mechanism that setup.py develop
uses to make "editable" packages.
Currently, pip needs to implement fairly horrible hacks to make legacy setup.py develop
builds work. It'd be great if setuptools could implement PEP 660, which would be the last item from setuptools' end before pip can start the process of removing the legacy directly-call-setup.py build system.
PEP 660's build_editable hook gets implemented in aetuptools.
Alternative SolutionsNot doing this.
I imagine this will mean that either (a) pip continues to maintain editable installs for setuptools or (b) pip drops the legacy build system entirely and users of setuptools projects will no longer be able to make editable installations.
I don't think (b) is happening any time soon, and it'd likely be best to implement the hook here.
Additional contextIIUC, this has been implemented in setuptools-pep660 already. It might not be a lot of work to migrate the work done there into seriptools directly.
Code of Conductbocklund, jaraco, astrojuanlu, 5j9, horsfallnathan and 19 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4