Various exceptions that appeared when moving from 2.2.2 to 2.3.11 #44
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
Codecov Report
@@ Coverage Diff @@
## develop #44 +/- ##
======================================
Coverage 100% 100%
======================================
Files 12 12
Lines 1203 1206 +3
Branches 213 213
======================================
+ Hits 1203 1206 +3
Continue to review full report at Codecov.
|
|
Thanks so much for this, @adam-iris. |
|
Thanks for the quick integration and release! |
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.
These are all based on content that parsed successfully (not necessarily correctly, but without raising exceptions) in version 2.2.2, but caused problems when we moved to 2.3.11. (See the added test cases for examples of the content that was failing -- this also addresses the Unicode exception in #43, although I neglected to add a test case for that.)
I used the PHP Textile code as a guideline for these, in a lot of cases the PHP code relies on behavior that's different from Python (for example, trying to pop an item off an empty list apparently returns a null item in PHP, but raises an exception in Python). I tried to handle these in a minimal way so that the structure of the code doesn't deviate too far from the PHP version.
The one test case I'm a bit unsure about is the first one in
test_urls.py-- if the link text starts with a space, the behavior is a bit unexpected (it quotes the whole line up to the link) but this matches the behavior of the PHP version.