Fixed BS html.parser error #17
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Really simple, Beautiful Soup was raising an issue about not explicitly specifying an HTML parser.
brahmcapoor did a similar PR, but I don't know if it ever passed travis.
So from:
To:
Please note that it still doesn't find the appropriate synonyms.
EDIT:
I'm still new to CI and travis, but I saw this error message:
nose.proxy.AssertionError: None is not an instance of <class 'list'>
Is this because each listed synonym string is under it's own individual span tag in the markup?
The code is currently scanning for child list items directly under this div container:
Either way that's why my travis tests failed.
That's for another PR I think.. Thank you.