Print

Print


> I got to make the install work by using `pip==23.0.1 setuptools==65.5.1`

I think constraining `setuptools` is unecessary as this is just running into

> * Remove `setup.py install` fallback when building a wheel failed for projects without `pyproject.toml`. ([#8368](https://github.com/pypa/pip/issues/8368))
> * When the `wheel` package is not installed, pip now uses the default build backend instead of `setup.py install` and `setup.py develop` for project without `pyproject.toml`. ([#8559](https://github.com/pypa/pip/issues/8559))

as outlined in the [`pip` `v23.1` release notes](https://pip.pypa.io/en/stable/news/#v23-1) — remember `pip` does not use SemVer but a custom CalVer like system!

@henryiii can correct me if I'm wrong, but until a modern build system can be established in Issue #1844 I see no problem with just pinning `pip` to a version that hasn't deprecated support for the legacy systems used now (i.e. `pip<23.1`).




-- 
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/2002#issuecomment-1558732158
You are receiving this because you are subscribed to this thread.

Message ID: <[log in to unmask]>

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1