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

Add Python 3.11 to CI & documentation #3090

Merged
merged 1 commit into from
Dec 22, 2022

Conversation

tomaarsen
Copy link
Member

Resolves #3089

Hello!

Pull Request overview

  • Add Python 3.11 to CI.
  • State support for Python 3.11 in documentation.

Details

As of 2022-10-24, Python 3.11 has been fully released. As such, it is high time to officially add support for it in NLTK. This involves updating documentation and the CI test suite to ensure correct behaviour in Python 3.11. In this PR, I have done so. I believe to have updated all of the places where all valid Python versions are mentioned.

  • Tom Aarsen

@tomaarsen
Copy link
Member Author

python-crfsuite fails to install on Python 3.11. See this related issue on its GitHub page: scrapinghub/python-crfsuite#150.
It's the only bottleneck preventing us from officially supporting Python 3.11.

@stevenbird stevenbird merged commit 3c04543 into nltk:develop Dec 22, 2022
@stevenbird
Copy link
Member

Thanks @tomaarsen. Hoping the issue with python-crfsuite goes away in due course.

@tomaarsen tomaarsen deleted the enhancement/support_py311 branch December 22, 2022 15:02
@tomaarsen
Copy link
Member Author

As for the failing tests - should we temporarily skip them, or should we just leave it be?

@stevenbird
Copy link
Member

I think it would be good if we temporally skipped the failing tests please, so new PRs don't show up as failing.

@tomaarsen
Copy link
Member Author

tomaarsen commented Dec 22, 2022

Agreed. I'll skip the failing tests regardless of Python version, that seems easiest.

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

Successfully merging this pull request may close these issues.

Safe to use on Python 3.11?
2 participants