Thanks, I already figured it out a few days ago.
In the wordnet.py file, just override the path (WNHOME and/or WNSEARCH)
to the wordnet 2.0directory that has the lexnames files etc... (on my
ubuntu box: '/usr/share/wordnet')
That seems to fix it, although python gives a few warnings at startup.
ch
vdrab wrote:
> I had WordNet 2.0 installed but just now I tried it with 1.7.1 as well
> and the result was the same. It's a shame, glossing over the pywordnet
> page really made me want to give it a try.
> Are there any workarounds you can recommend ?
What's your wordnet setup like? I have mine i
hello Steve,
I had WordNet 2.0 installed but just now I tried it with 1.7.1 as well
and the result was the same. It's a shame, glossing over the pywordnet
page really made me want to give it a try.
Are there any workarounds you can recommend ?
I had a quick look at the wordnet.py file, and it look
vdrab wrote:
> hello pythoneers,
>
> I recently tried to install wordnet 2.0 and pywordnet on both an ubuntu
> linux running python 2.4 and a winXP running activePython 2.4.1, and I
> get the exact same error on both when I try to "from wordnet import *"
> :
>
> running install
> error: invalid P
hello pythoneers,
I recently tried to install wordnet 2.0 and pywordnet on both an ubuntu
linux running python 2.4 and a winXP running activePython 2.4.1, and I
get the exact same error on both when I try to "from wordnet import *"
:
running install
error: invalid Python installation: unable to o
