Michael Wayne Goodman

> I think what we'll probably do here is have `url_for` return a `URL` instance, and add a `.with_query_params` method to URLs I like this idea but I'm concerned that...

> I think these are the authors of the last example in the `ss.examples()` list, that haven't been parsed as part of the example because they aren't within the double...

@genericallyterrible thanks for the nice analysis, list of examples, and proposed solution. If the NLTK's wordnet module continues to receive maintenance, I think your solution would be useful. If, instead,...

I've thought about this a bit more. I'm not sure we should try to extract multiple definitions. From the [WNDB docs](https://wordnet.princeton.edu/documentation/wndb5wn) (emphasis added): > - *gloss* > Each synset contains...

I've been consulting with @alvations and @fcbond to work on an entirely new wordnet module: https://github.com/goodmami/wn. It's not yet feature-complete nor documented (contributions are welcome), but the basics are working...

Hi, returning to this with an update: the Wn library has been, since shortly after my last comment, [documented](https://wn.readthedocs.io/en/latest/) and reasonably feature-complete since the 0.8.0 release about four months ago....

> We could try to (a) replace the existing module, or (b) give people a choice of both? In terms of long term ease of maintenance, I favor (a). We...

> it doesn't seem to have a "sense key" notion, although sensekeys are the only reliable identifier across Wordnet versions This is because sense keys are not a core part...

An update: I've pushed the current state of my NLTK-compatibility shim to Wn in the `nltk` branch. Here is the relevant file: https://github.com/goodmami/wn/blob/nltk/wn/nltk_api.py It uses Wn under the hood, but...

@alvations I don't think we would gain much by using a full parser like [ACE](http://sweaglesw.org/linguistics/ace/) just for tokenization, unless you also want morphological analysis, or pronoun detection, or quantifier scope,...