-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PROJ 6.1+ (pyproj 2.2+ wheels) incompatible with previous versions #368
Comments
It would be nice to at least be able to detect it to give a more informative error message to the user. But, I would think it should actually be solvable (although in the end, it is a quite fundamental difference between pip and conda how they handle dependencies ..). |
Since the so name of the included proj library gets mangled, shouldn't the pyproj wheel be able to get the correct proj lib? (the one included) Even when there are other libraries with the same name available on the system |
The part that has me confused is that it works with PROJ 6.0.0 but not with 6.1.1. I am curious as to what changed between the versions that might impact that. |
I wonder if it has to do with the version of cython used? They have had some releases recently https://github.com/cython/cython/releases |
On my manjaro system I have and in virtual env I have but I get the following error on import of cartopy libproj.so.13: cannot open shared object file: No such file or directory I have these versions of libproj on my system I assume this problem is related to this bug. |
@aspedisca cartopy does not use pyproj. I would recommend opening an issue on the cartopy repo. |
This may help you: SciTools/cartopy#1289 (comment) |
I am hoping this will finally be addressed in 2.3.1 🤞 |
Fix confirmed:
|
Related to:
Problem:
When proj<6 is installed in the environment and a pyproj wheel with PROJ 6.1+ is installed, a segfault occurs.
Steps to reproduce:
However, if you install a version with PROJ 6.0.0, it works okay:
Still fails with
pyproj==2.1.3
with PROJ 6.1+PROJ error location
Seems to be:
The text was updated successfully, but these errors were encountered: