add importlib-metadata, https URLs, remove setuptools

[bollwyvl]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

Notes:

• alternative to Add importlib-metadata dependency #115
• updates for https urls

Fixes #114

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jakirkham]

Thanks Nick! 😄

Had a few questions below. Also does this need a build number bump?

[jakirkham]

Do we have importlib-metadata on Python 3.10+? What happens when it is installed there? How does this interact with the builtin importlib.metadata when available?

[bollwyvl]

Do we have importlib-metadata on Python 3.10+? W

We do, back to e.g. linux-64/importlib-metadata-4.8.1-py310hff52083_1.tar.bz2

What happens when it is installed there

Nothing too freaky... it doesn't shadow the builtin (importlib.resources) or anything.

interact with the builtin importlib.metadata when available?

In the cases I've found, it looks like it will preferentially import from the separate package before trying the builtin.

[jakirkham]

Interesting would have thought the builtin would be tried first. Have asked about that ( sphinx-doc/sphinx#10007 (review) ).

[bollwyvl]

looks like it was answered... again, it's highly likely some package in a good-sized sphinx env is going to have the latest-and-greatest importlib because a lot of authors (pragmatically) can't be bothered to do pins, and i don't blame them. if it can't deal with the backport, then there are bigger problems, and if python keeps changing the API, this problem will basically never go away.

[jakirkham]

Yep agreed. Am use to seeing the other import order as the backport package is pretty static and eventually fades out of existence. There are of course exceptions like mock. Seems like this is more like mock than other backport packages.

If things become more fragmented, like the backport package should be used for certain Python versions and not others, we may need revisit dropping noarch.

Though hopefully things settle down eventually.

[bollwyvl]

@conda-forge-admin please rerender