-
Notifications
You must be signed in to change notification settings - Fork 70
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
Serializer still depends on GDAL? #75
Comments
That's a string from Can you check the type of your |
I can confirm this, had the same issue on arch after installing |
the same problem, after |
Confirmed - with the same solution as mentioned above. Not really surprising considering the following import pattern is used throughout django-geojson & django-leaflet: # from django-geojson serializers.py
try:
from django.contrib.gis.geos import WKBWriter
from django.contrib.gis.geos import GEOSGeometry
from django.contrib.gis.db.models.fields import GeometryField
except (ImportError, ImproperlyConfigured):
from .nogeos import WKBWriter
from .nogeos import GEOSGeometry
from .fields import GeometryField As |
Encountered the same since I updated to 2.11.0 :( (the bug is not present in 2.10.0) |
You can check the diff @Gagaro could you update the Github releases page please? And also, use PRs where Travis tests remain green instead of committing to master (easier to follow regressions etc.). Thanks! |
Travis tests are green, the only PR I merged without travis was the pip install one which was very simple (but still needed travis...). And yes I should update the releases. |
Is there any chance that this issue could be resolved? I just started using django-geojson, and I'm getting the same error as @flesser for apparently the same reason. I don't want to install gdal just to make an import I don't plan to use not crash. I cannot downgrade to 2.10 because my project uses Django 2.x. |
I encountered a strange issue. On my development machine, everything worked fine. When I tried to run my project on another computer, I suddenly got errors like the following when saving a PointField:
After performing a
sudo apt-get install gdal-bin
(which also installed a whole bunch of other geospatial libraries), the errors were gone. But the whole point of using django-geojson is that I don't need to install geospatial libraries just to store some Points and have nice Leaflet widgets.On both computers, Django runs in the same freshly installed Python3-virtualenv:
The text was updated successfully, but these errors were encountered: