[Snyk] Security upgrade nltk from 3.3 to 3.10.0

[brookecastleberry]

Snyk has created this PR to fix 4 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• pip-sample/requirements.txt

⚠️ Warning

jupyter-console 6.6.3 has requirement ipykernel>=6.14, but you have ipykernel 5.0.0.
jupyter-console 6.6.3 has requirement jupyter-client>=7.0.0, but you have jupyter-client 5.2.3.
jupyter-console 6.6.3 has requirement traitlets>=5.4, but you have traitlets 4.3.2.
jupyter-console 6.6.3 has requirement jupyter-core!=5.0.*,>=4.12, but you have jupyter-core 4.4.0.
Jinja2 2.10 requires MarkupSafe, which is not installed.
ipython 7.34.0 has requirement jedi>=0.16, but you have jedi 0.12.1.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal
🦉 Server-side Request Forgery (SSRF)
🦉 Regular Expression Denial of Service (ReDoS)

[brookecastleberry]

This upgrade spans several minor versions and introduces significant changes to environment requirements and package behavior, warranting a medium risk assessment.

Key Breaking Changes:

• Python Version Requirement: The most critical change is the required Python version. nltk@3.10.0 requires Python 3.10 or newer. The starting version, nltk@3.3, supported Python 3.6. Support for Python versions 3.7, 3.8, and 3.9 was dropped in subsequent releases. Your environment must be running at least Python 3.10 to support this upgrade.

• WordNet Sorting Behavior: Starting with nltk@3.9, WordNet synsets and relations are no longer sorted by default. Any code that relies on the previously consistent sorted output of WordNet functions may break or behave unexpectedly. You must now explicitly sort the results in your own code if a specific order is required.

• Moses Tokenizer Removed: The moses.py tokenizer was removed in version 3.3 due to an incompatible license. If your project was using this tokenizer, you will need to find an alternative.

Recommendation:
Before merging, verify that your production environment and CI/CD pipelines are running Python 3.10 or a more recent version. Review any code that interacts with WordNet to ensure that the change in sorting behavior does not affect your application's logic.

Source: NLTK Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.