Networkx 3.3 doesn't support Python 3.9 anymore

[danielbrown2]

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.

Networkx 3.3 dropped Python 3.9 networkx/networkx#7028

The recipe for this feedstock hasn't been updated properly though: https://github.com/conda-forge/networkx-feedstock/blob/main/recipe/meta.yaml#L18

[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.

[h-vetinari]

Thanks for this!

[h-vetinari]

FWIW, we need to fix the repodata anyway (because build _0 would still remain "compatible" with 3.9, according to the metadata), see conda-forge/conda-forge-repodata-patches-feedstock#697. This PR should still be merged because we need the updated lower bounds going forward.

[RMeli]

Thanks! I just bumped into this issue too.

[RMeli]

This has been an issue for the previous release as well, see #52 and networkx/networkx#7039. Is there a way to put some checks in place?

[h-vetinari]

This has been an issue for the previous release as well, see #52 and networkx/networkx#7039. Is there a way to put some checks in place?

Not easy to do with the current setup; we'd need to build it once and test it against several python versions, which conda-build doesn't support.

[h-vetinari]

It's basically up to the maintainers to be careful about this and check what upstream is doing, before pressing merge just because the CI is green.

[h-vetinari]

Now that conda-forge/conda-forge-repodata-patches-feedstock#697 fixed this, let's put this in so we have a release-able state on main again.

[RMeli]

which conda-build doesn't support

I see, thank you for the clarification.

[MridulS]

It's basically up to the maintainers to be careful about this and check what upstream is doing, before pressing merge just because the CI is green.

Urghh my bad. Thanks for taking care of this everyone!!

[MridulS]

Also fwiw, I should also have updated the constrained deps.