-
Notifications
You must be signed in to change notification settings - Fork 10
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix nltk dependency #536
Fix nltk dependency #536
Conversation
Use the last version that supports Python 2.7. Fixes #533.
@spoeschel the build fails, but not obviously because of the change to a specified version of nltk. I think we may need to resolve some other issue first, but I'd be happy to do it in the same pull request. What do you think? |
With version 3.2.1 of Pytest-BDD, the error doesn't occur and the (non-skipped) tests all pass. That version is actually the same one that automatically was used by the most recent passing Travis builds. The two errors that show up with a recent version are caused by the comments that are present at the line ends of some feature example tables (example). While moving the comments to a separate line fixes the errors, the tests still don't pass. Hence this seems to be a larger issue. So I think the easiest solution would be:
Would this be OK for you? |
Ah, that problem. We've already fixed that in the BBC python3 fork. Yes, happy to pin the Pytest-BDD version for the python2 branch to make a release that works. |
As versions newer than 3.2.1 don't work with the test suite, use the last working version, as a maintenance fix to this legacy branch. Addresses #537 regarding the legacy Python 2 branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @spoeschel this looks good to me. I changed the target branch to release/2.1.3 following the normal procedure of creating a release staging branch. When we want to make a release we'll pull the changes from release/2.1.3 into master and create the release tag.
Feel free to merge this!
Thanks, @nigelmegitt! I will have a look at possible further maintenance fixes for a 2.1.3 release. |
Use the last version that supports Python 2.7.
Fixes #533.