[Snyk] Security upgrade nltk from 3.6.2 to 3.9.3

[ryanmcmorrowsnyk]

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

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

inflect 6.0.5 has requirement pydantic<2,>=1.9.1, but you have pydantic 1.8.2.
graphql-relay 3.1.0 has requirement typing-extensions<4,>=3.7; python_version < "3.8", but you have typing-extensions 4.7.1.
google-api-core 1.34.1 has requirement protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<4.0.0dev,>=3.19.5, but you have protobuf 4.24.4.

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

[ryanmcmorrowsnyk]

This upgrade for NLTK from version 3.6.2 to 3.9.3 introduces several changes that require verification, primarily related to Python version compatibility and specific behavioral modifications.

Key Changes:

• Python Version Support: Support for Python 3.6 was dropped in NLTK 3.7, and support for Python 3.8 was dropped in NLTK 3.9.2. The target version 3.9.3 requires Python 3.10 or newer.
• Behavioral Change in WordNet: Starting with version 3.9, NLTK no longer automatically sorts WordNet synsets and relations. If your application relies on a sorted output from these functions, you must now explicitly sort the results in your code.
• Behavioral Change in METEOR: In version 3.6.5, the METEOR evaluation metric now requires pre-tokenized input, which may require changes if you use this function.
• Security Fix: Version 3.9 and later replace pickled models with a new format to address a security vulnerability (CVE-2024-39705). This is unlikely to affect most users but is a significant internal change.

Recommendation:
Verify that your environment is running Python 3.10 or newer. Review any code that uses WordNet synsets or the METEOR evaluation function to ensure compatibility with the new behaviors.

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.