We're seeing this issue when running our

At a glance

The community members are experiencing an issue where the "Resource wordnet not found" error occurs when running their project and doing a fresh install of dependencies. A community member suggests this is related to a known issue with NLTK version 3.9. The discussion explores potential solutions, including pinning the NLTK version to 3.8.1 or using the pre-release version 3.9b1, which may have security vulnerabilities. The community members also create an issue in the llama index repository to track this problem.

Useful resources

MMike

We're seeing this issue when running our project and doing a fresh install of the dependencies. Anyone else experiencing this or know what could cause this?

"Resource wordnet not found. Please use the NLTK Downloader to obtain the resource:"

14 comments

MMike

It looks like this is the issue: https://github.com/nltk/nltk/issues/3308

MMike

@Logan M does llama index use nltk >= 3.8.1 as a version? Probably safer to pin that to a version. Seems like nltk 3.9 is in a broken state currently.

LLogan M

Riperoni

LLogan M

I don't thiiiink any of the features we use are broken

LLogan M

Could be wrong

LLogan M

Ah I see, this was released just a few hours ago 🤦‍♂️ I was avoiding pinning it because I was trying to avoid installing a cve. It's been a bit of a fiasco over there

MMike

yea this issue is very new...

MMike

adding nltk==3.8.1 to my requirements.txt does fix the issue

MMike

I've created an issue for this in the llama index repo: https://github.com/run-llama/llama_index/issues/15470

MMike

using nltk==3.9b1 is probably better as I believe there are some security vulnerabilities in 3.8.1. 3.9b1 is a pre-release version though.

LLogan M

Yea poetry does not play nice with beta versions in toml files.

For now, I set the dependency to be nltk = ">=3.8.1,!=3.9"

LLogan M

So users can install the prerelease if they want, and when nltk updates again, it will catch it

MMike

Nice one @Logan M ! Thanks for picking this up so quickly.

LLogan M

💪

Add a reply

Find answers from the community

We're seeing this issue when running our