If you try to loop through senses first, hypernym_paths() hangs about wn HOT 5 CLOSED

from wn.

This is odd. I suspect the Sense.synset() method is not creating a synset object in the same way as via the Wordnet.synsets() method, and then the hypernym_paths() method attempts to expand through all installed wordnets. If so, then it should be an easy fix.

edit: here's a shorter MWE:

import wn
en = wn.Wordnet('omw-en:1.4')
en.sense('omw-en-beast-00015388-n').synset().hypernym_paths()

from wn.

Looks like my guess was correct. Here is Sense.synset():

Note that it calls the module function wn.synset(), without any limits on the lexicons. The resulting, unconstrained synset will then use any installed lexicon to look for expanded relations on subsequent operations. It would be better to construct a Synset like how Wordnet.synset() does:

But the lexicon_rowids constraint on the call to find_synsets would need to be filled out. If a Wordnet object was used to get the sense, it would just be self._wordnet._lexicon_ids, but not if the query was done in "default mode" (which I thought was documented, but now I don't see it in the docs; see #92 (comment)). Luckily there's a non-public convenience method for this:

Secondly, the wordnet object of the sense (accessible via the _wordnet attribute) needs to be passed in the Synset constructor instead of just self.

Finally, it looks like Sense.word() has the same issue.

I'm going to assign this to you, @fcbond. If that's ok, please submit a PR and I'll look it over. If not, I can do it.

from wn.

@fcbond just checking in. Do you think you can do this, or shall I?

from wn.

The synset issue was apparently resolved in #170. Sense.word() still has the same problem, though.

from wn.