Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Removed ORGException causes issues when using GeoDjango after 2.0 #205

Closed
rtpg opened this issue Sep 7, 2019 · 1 comment
Closed

Removed ORGException causes issues when using GeoDjango after 2.0 #205

rtpg opened this issue Sep 7, 2019 · 1 comment
Labels
Bug Probably Easy Issues that should be easy for someone to resolve. Good for first timers :)

Comments

@rtpg
Copy link
Contributor

rtpg commented Sep 7, 2019

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

Originally posted by @igorkurochka in #203 (comment)
@rtpg rtpg added Probably Easy Issues that should be easy for someone to resolve. Good for first timers :) Bug labels Sep 7, 2019
This was referenced Sep 7, 2019
Merged
Closed
@rtpg
Copy link
Contributor Author

rtpg commented Sep 7, 2019

This issue is fixed inside of #209

@rtpg rtpg closed this as completed Sep 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Probably Easy Issues that should be easy for someone to resolve. Good for first timers :)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rtpg