Bump to Python >= 3.8

[johnhany97]

With jaraco/zipp@4269d27, consumers still on python 3.7 may end up picking this up and failing at runtime.

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.

[conda-forge-webservices]

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.

[johnhany97]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/zipp-feedstock/actions/runs/5508647844.

[johnhany97]

@nehaljwani would appreciate if you could review this PR at your earliest convenience

[dtreichler]

The build current on conda-forge breaks python 3.7 environments. Is it possible to retract or otherwise patch the existing package?

[nehaljwani]

One can open a PR at https://github.com/conda-forge/conda-forge-repodata-patches-feedstock for patching the repodata.

[h-vetinari]

The build current on conda-forge breaks python 3.7 environments.

While we shouldn't break things gratuitously (and I'm fine with fixing this case), Python 3.7 is end-of-life and has been completely dropped by conda-forge since almost a year.

It should be considered completely unsupported, and I strongly recommend to upgrade your pythons ASAP.