You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue came up recently where setuptools and hatchling/scikit-build-core either normalize or do not normalize the project name when creating the *.dist-info folder. My understanding is that this should not be an issue because tools like importlib.metadata should also do such normalization, but apparently pkg_resources.requires fails at that. The complication is also that that function is deprecated (and removed) in more recent setuptools so I cannot check it locally what is the status there.
But in short, is the normalization backed by a PEP, and if so why is it not enforced on setuptools?
Thanks for the reference. I guess it's an issue on setuptools that they should align to it. But interesting that the upstream bug in pkg_resources says that jaraco.functools is failing, but the version in EPEL9 is reported to actually pass 🤷. My thought right now is to make a symlink to satisfy the issue in that bugzilla, but I don't know if it can cause other unforeseen issues. Hopefully though this is a user issue that can be solved by using importlib.metadata.
This issue came up recently where
setuptools
andhatchling
/scikit-build-core
either normalize or do not normalize the project name when creating the*.dist-info
folder. My understanding is that this should not be an issue because tools likeimportlib.metadata
should also do such normalization, but apparentlypkg_resources.requires
fails at that. The complication is also that that function is deprecated (and removed) in more recentsetuptools
so I cannot check it locally what is the status there.But in short, is the normalization backed by a PEP, and if so why is it not enforced on
setuptools
?Reference:
The text was updated successfully, but these errors were encountered: