Skip to content
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 #2444 by having a special case for py 2.7 #2446

Merged
merged 1 commit into from Nov 12, 2019
Merged

Fix #2444 by having a special case for py 2.7 #2446

merged 1 commit into from Nov 12, 2019

Conversation

sildar
Copy link

@sildar sildar commented Oct 30, 2019

As Python 2.7 is still marked as supported by NLTK, version 3.4.5 shouldn't break compatibility.

This fixes #2444 which is one instance of regression that I was faced with. AFAIK, there are no other regressions.

@sildar sildar changed the title Fix #2444 by havign a special case for py 2.7 Fix #2444 by having a special case for py 2.7 Oct 30, 2019
@sildar
Copy link
Author

sildar commented Oct 30, 2019

Failed tests are identical to tag 3.4.5 https://travis-ci.org/nltk/nltk/jobs/574281125

@stevenbird stevenbird merged commit 6b0312a into nltk:3.4.5 Nov 12, 2019
@stevenbird
Copy link
Member

Thanks @sildar

@sildar
Copy link
Author

sildar commented Nov 18, 2019

@stevenbird Will there be a new release including this fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants