Open DManowitz opened 6 months ago
Thanks for pointing this out. I am testing pyproj<3.5.0
in #297.
@mmann1123 #297 tests passed with the relaxation of the pyproj
version. Do you see any reason not to merge these changes?
No I can't think of any reason
@DManowitz the latest release (v2.1.16) has support for pyproj<3.5.0
. If that geowombat version is working for you then I think we can close this issue. Thanks again for highlighting this.
Once this version posts to conda-forge, I will try it out.
I am going to close this, but feel free to reopen.
@jgrss Have you tested this package with pyproj >=3.6.0? When I opened this issue previously, I was using python 3.8, but I'm trying to move to python 3.10 now, and I'd like to be able to use the more recent pyproj libraries, if possible.
I will test pyproj>=3.6
and see if we can upgrade the requirement.
In setup.cfg, I see a comment that pyproj 3.5.0 causes an error. However, the pin is on
pyproj <=3.4.0
rather thanpyproj <3.5.0
. Does this same error happen with pyproj 3.4.1, and if not, could the pin be changed?