bug fixes for blogger blog id parsing #15
Merged
Conversation
This file contains hidden or 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
specifically: * handle new style blogger blog ids prefixed with g. details in snarfed/bridgy#168 * don't crash if blog id can't be parsed. details in bridgy/issues#147 ported from snarfed/gdata-python-client-1@e1404ec
dvska
approved these changes
Nov 28, 2019
Contributor
Author
|
thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
specifically:
i filed this against the original repo a while back, in google/gdata-python-client#27. it was never merged (heh), but i still use gdata from my fork, and i'm now porting my app to Python 3, so i'd love to use your port. thank you so much for working on it!