Filipe Laíns 🇵🇸

Yes. In practice, this is only relevant to CPython right now, where debug builds can load both debug and non-debug modules, but we want the debug tag in that case.

That would be useful. It would allow us replace usages such as this ```python requirement = packaging.requirements.Requirement(requirement_string) if requirement.marker: # append our extra to the marker requirement.marker = packaging.markers.Marker( str(requirement.marker)...

This is just an initial proposal for the fix. @lawrence-danna-apple can you clarify on the Apple policy? Is the version only omitted starting from 12 and onwards? Is it always...

No, sorry. I wasn't clear enough. I am asking for a way to validate if the requirements are met. This can be used for eg. in python-build to validate the...

I have a minimal implementation, but it does not validate the dependencies of extras. It would be good to have a strong implementation here, since it turns out it is...

Yes.

I agree, we should consider if we should use `importlib.metadata` or something else. I would say the `importlib-metadata` dependency is just a temporary nuisance, `importlib.metdata` is available from Python 3.8...

But it would need to use the functionality provided by `packaging`. As `importlib` is part of the standard library, this is not possible. I agree `packaging` might not be the...

I think it makes more sense to have it here. This library aims to provide "Core utilities for Python packages", I think verifying if the requirements are met is one...

We have a working implementation in pypa/build. How do we want to proceed?