Fix docstring with misleading/wrong order of latitude and longitude in geopy/point.py #229
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Btw - I searched the whole project for similar glitches and did not find any. |
|
This is a duplicate of an older PR #207 which just has been merged, so I'm going to close this. But thank you anyway! |
|
Sorry for missing PR #207 and thanks for fixing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I stumbled upon a tiny glitch in
geopy/point.pyin line 59 and line 64. Looks like someone accidentally swappedlatitudeandlongitudein thePointclass' docstring. If you're reading the documentation on readthedocs (as I did) this can be quite misleading. This pull request swaps the two parameters back into the right order, hence it does not touch any code, just the docstring.Nevertheless thanks for your patience and your excellent work so far !
Cheers,
Stephan