Skip to content

Add geopy #160

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

Merged
merged 1 commit into from
Dec 3, 2018
Merged

Add geopy #160

merged 1 commit into from
Dec 3, 2018

Conversation

KostyaEsmukov
Copy link
Contributor

@KostyaEsmukov KostyaEsmukov commented Dec 2, 2018

This PR adds geopy project.

The release date for geopy 2.0 (which will drop 2.7 support) is somewhat flexible, but I expect it to happen in ~2019Q2 (this is also written at https://geopy.readthedocs.io/en/1.18.0/#geopy-2-0 and geopy/geopy#292).

@takluyver
Copy link
Member

Thanks, welcome aboard! If you want any pointers about making the transition, feel free to ask.

(Confirmed that @KostyaEsmukov is the main recent contributor to Geopy)

@takluyver takluyver merged commit a2cfa7d into python3statement:master Dec 3, 2018
@KostyaEsmukov KostyaEsmukov deleted the add-geopy branch December 3, 2018 19:25
@mscuthbert
Copy link
Collaborator

It's incredible watching "major" projects like geopy appearing in the middle(!) of the list and seeing the whole list continue to grow. The tide has turned. Python 3 will not be Perl 6.

@takluyver
Copy link
Member

Yup, there were some uncertain moments, but it's great to see the transition happening.

When we started drafting this statement, I likened our projects to migrating wildebeest standing nervously on the bank of a river. Any one crossing alone risks getting eaten by crocodiles, but if they can see each other crossing, they'll charge on. This metaphor may not be biologically all that accurate, but I still like the idea. :-)

@KostyaEsmukov
Copy link
Contributor Author

@takluyver this is a great metaphor! Indeed, the more projects join the "herd", the stronger the arguments for abandoning 2.7 sooner than its EOL.

While we are here, I would like to thank everyone involved in putting up such a thoughtful and persuasive statement, which is a genuine pleasure to sign and share. 🎉

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

Successfully merging this pull request may close these issues.

3 participants