I do note that using import distutils rather than the vendored copy does work.

The point of PR #1700 was to move off distutils as it is being deprecated, as @henryiii mentioned.

There I was already trying to do the guard that @henryiii suggests

https://github.com/xrootd/xrootd/blob/8e1e528232d8ead08468eefcbf991737eb5751da/bindings/python/setup.py.in#L3-L19

though as to

Where does the import setuptools fail, though?

this was attempted in PR #1585, but

This PR was meant to also change:

but it seems that these are still required given the current state of the build and will need to be revised in a later PR.

I don't remember where exactly this failed, so let me post this and rerun the Docker build that is described there.


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/1830/1332674267@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1830#issuecomment-1332674267", "url": "https://github.com/xrootd/xrootd/issues/1830#issuecomment-1332674267", "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