In another issue we received a report that GeoDjango support is broken in 2.0 thanks to an exception being removed/merged together.
Ideally, a fix with this comes with a set of tests that would have caused this error to be caught in the test suite.
@rtpg I've found one more onresolved issue, floppyforms/gis/widgets.py, line 87 uses gdal.OGRException which was removed after merged with GDALException in Django 1.8 https://code.djangoproject.com/ticket/28559
would be great if you resolve this in your fork. thanks
rtpg
commented
5 years ago
In another issue we received a report that GeoDjango support is broken in 2.0 thanks to an exception being removed/merged together.
Ideally, a fix with this comes with a set of tests that would have caused this error to be caught in the test suite.
@rtpg I've found one more onresolved issue, floppyforms/gis/widgets.py, line 87 uses
gdal.OGRExceptionwhich was removed after merged with GDALException in Django 1.8 https://code.djangoproject.com/ticket/28559would be great if you resolve this in your fork. thanks
Originally posted by @igorkurochka in https://github.com/jazzband/django-floppyforms/pull/203#issuecomment-516762933