- Notifications
You must be signed in to change notification settings - Fork121
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Add geopy#160
Uh oh!
There was an error while loading.Please reload this page.
Conversation
takluyver commentedDec 3, 2018
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) |
mscuthbert commentedDec 4, 2018
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 commentedDec 4, 2018
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 commentedDec 4, 2018
@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. 🎉 |
Uh oh!
There was an error while loading.Please reload this page.
This PR addsgeopy 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 athttps://geopy.readthedocs.io/en/1.18.0/#geopy-2-0 andgeopy/geopy#292).