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

Mention django GEOS bug in README #393

Closed
edwardgalligan opened this issue Dec 15, 2017 · 1 comment
Closed

Mention django GEOS bug in README #393

edwardgalligan opened this issue Dec 15, 2017 · 1 comment

Comments

@edwardgalligan
Copy link

edwardgalligan commented Dec 15, 2017 •
edited
Loading

Just ran across a django bug with parsing GEOS version numbers that causes the application to crash on startup. It's documented here: https://code.djangoproject.com/ticket/28441

The fix is either upgrading to Django 1.11 (#379) or downgrading GEOS to 3.6.1 (as later versions trigger the django bug).

Might be worthwhile sticking a note about the downgrade workaround in the README until #379 is resolved (I'll submit a PR).
@josokinas
Copy link
Member

Closing this as latest GeoKey version now supports Django version 1.11 🥇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edwardgalligan @josokinas