Create v3.2.x abi migration branch?

[akrherz]

Issue: pyproj 3.3 requires python 3.8+, creating dependency island for repos still supporting 3.7

For example: conda-forge/cartopy-feedstock#135 , which is attempting to migrate proj=8.2.1 and failing due to no python=3.7 + pyproj + proj=8.2.1 builds.

Would it make sense to create a abi_migration_branches of v3.2.x here? I am happy to help make that happen.

[xylar]

The alternative is presumably to drop python 3.7 support in cartopy and other downstream packages.

[snowman2]

pyproj4/pyproj#930

[ocefpaf]

The alternative is presumably to drop python 3.7 support in cartopy and other downstream packages.

Kind of makes sense since we are "kind of" following NEP 29 and that dropped support for 3.7 last month.

[akrherz]

Thanks for the rapid responses everyone! I am fine with dropping python 3.7 when this issue comes up. I made the cartopy PR and am closing this issue here.