In the longer term, I think I will just take some time to write new python packaging code following PEP 517 and PEP 632, dropping usage of deprecated stuff altogether.

Originally posted by @amadio in #1830 (comment)

@henryiii also wrote

I'd try dropping in a pyproject.toml with:

[build-system]
requires = ["setuptools>=42"]
build-backend = "setuptools.build_meta

And just seeing what happens. I'd try that, but I'm not sure how to trigger the generation properly.

I think this is a great idea overall. There's a lot to modernize, especially as setup.py ends up calling packaging/wheel/install.sh

https://github.com/xrootd/xrootd/blob/8e1e528232d8ead08468eefcbf991737eb5751da/packaging/wheel/setup.py#L168

I don't have time to contribute to this, but if there was someone else who wanted to give this a go, and if @henryiii thought scikit-build was ready, I think it would be super interesting to see XRootD jump right to using scikit-build (and hopefully missing a lot of pain along the way). People with much more experience than me though hopefully have some more informed thoughts.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1844@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1844", "url": "https://github.com/xrootd/xrootd/issues/1844", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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