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.

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

django.contrib.gis.geos.error.GEOSException: Could not parse version info string "3.6.2-CAPI-1.10.2 4d2925d6" #3297

Closed
kakulukia opened this issue Nov 22, 2017 · 6 comments

Comments

@kakulukia
Copy link

kakulukia commented Nov 22, 2017

python 2.7.14 and 3.6.3 on OSX

Whats happening here?

I also found this bug ticket: https://code.djangoproject.com/ticket/28441
I cant downgrade geos like suggested: "Error: geos does not have a version "3.6.1" in the Cellar.
Versions available: 3.6.2"
looks like its only fixed in 1.11.5 but RTD doesnt run with 1.11.5

HELP!

@RichardLitt
Copy link
Member

Hey @kakulukia, thanks for opening an issue. Can you use the issue template that was provided, and explain the steps that led to this error? Thank you.

@kakulukia
Copy link
Author

Well the issue template is for online projects only, but as i said above im tried to get it to work on my osx machine and i was just following the installation instructions.
Nevertheless i manages to patch rtd to work with the latest Django version which suprisingly didnt took that much effort.

#3305

@tony
Copy link
Contributor

tony commented Dec 17, 2017

Also experienced this. See also: https://code.djangoproject.com/ticket/28441

@kakulukia kakulukia reopened this Dec 18, 2017
tony pushed a commit to kakulukia/readthedocs.org that referenced this issue Dec 18, 2017
tony pushed a commit to kakulukia/readthedocs.org that referenced this issue Dec 19, 2017
@stsewd
Copy link
Member

stsewd commented Nov 28, 2018

We already run on django 1.11 🎉 #4750

@stsewd stsewd closed this as completed Nov 28, 2018
@kakulukia
Copy link
Author

You shouldnt party that hard when theres a 2.1.3 and major changes ahead! :P

@davidfischer
Copy link
Contributor

You shouldnt party that hard when theres a 2.1.3 and major changes ahead! :P

I think being on the latest LTS is where we ought to be. I am looking forward to 2.2 though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants