Pradyun Gedam
Pradyun Gedam
I'd like to pull this discussion away from what functionality `setuptools-scm` provides or how it is designed or how interacts with parts of the ecosystems. And... with that, I'll highlight...
> This is of limited use right now, since there aren't many viable backends to move to. Yea. FWIW, there's a grant proposal submitted for https://github.com/scikit-build/scikit-build to work on [making...
For setuptools, the relevant issues are https://github.com/psf/fundable-packaging-improvements/issues/25 and https://github.com/pypa/setuptools/issues/1688. 🤷🏽
> ~halt of my packages is using setuptoolssphinx integration That's a choice that you've made. Those projects can equivalently be built with Sphinx directly as well.
Picking up from #462, the way that Python Packaging is modelled nowadays to use wheels as an intermediary for distribution/sharing an installable artifact. It's roughly equivalent to a binary RPM...
> Current policy for buildroot is we always build from sdists and never download wheels from pypi. Right, that's a very weird way of saying no. :) Anyway, that's basically...
Can you run the failing pip install run with `-vvv` and post the output of that?
Same as #41.
Indeed. I misread in a hurry. Sorry!
Hiya! > I wanted to use it to install pip into an own `pip` folder alongside `python` folder. You can't do that. The way that the Python interpreter works is...