I also recently encountered this issue in my project's build pipeline. It looks to me like the problematic setuptools.extern was added (d4b9bf98) in the 3.0.0 release and has since been removed (3bbc4696) from the latest code in main, but that newer commit has not been released. So, the maintainers here need to cut a new 3.0.2 or 4.0.0 release with the updated code.

If you can't wait for the new release, you may want to try declaring a requirement for an older version like python-daemon<3.0.0 to see if that works around this build issue. That's what I did in my project (https://github.com/quipucords/quipucords/pull/2714), and so far things seem to be building and working fine. (My project does not use python-daemon directly; my project uses ansible-runner which then requires python-daemon, and thankfully ansible-runner does not specify a minimum version for python-daemon.)

@brasmithredhat thanks for weighing in here, can I ask when would be the new release? If soonish, I can certainly wait a bit. Thanks!

I wish I knew! :smile: I'm not a maintainer for python-daemon, and I just fell into this issue as I was trying to solve build issues in my unrelated project. I suspect you and I are not the only ones affected, though, and I hope that the maintainers will cut a new release soon.

However, the last 3.0.1 release was more than a year ago, and the last commits to main were 8 months ago. That makes me worry that this project may be abandoned. (I'd love to be proven wrong!) So, you may want to implement a workaround now like I did rather that wait.

yeah, I just dropped @bignose an email about the new release thing, let's see

there is a setuptools.extern issue of accessing packaging starting setuptools starting v71, see https://github.com/pypa/setuptools/issues/4498 for further discussions

This was addressed in bug report #73 (closed 2023-03-08). As @brasmithredhat correctly notes, this fix did not get released in the past year, so I don't blame anyone for reporting the bug again.

I have now released ‘python-daemon’ version “3.0.2”, including the fix for bug report #73 (and this bug report also, if I'm correct that this is a duplicate).

yeah, totally, thanks for the release!

Thank you very much for the swift response, @bignose !!

actually you might want to take a look, the release is not successful

@chenrui You may also want to follow https://pagure.io/python-daemon/issue/94 since that's the issue that resulted in yanking the 3.0.2 release.

noted, thanks for the pointer :thumbsup: