Steven Bird

It's all down to what people want to contribute...

Many thanks @jeslinpjames ... unfortunately some issues to look at, but hopefully not hard to resolve.

@VirgisM: I think the existing implementation behaves as the documentation says, no?

Thanks for these suggestions @goodmami. So default behaviour would be to use a lemmatizer if available else proceed without (issuing the warning). The only change required will be for users...

Do any of the public methods that call ``_related()`` have docstrings that promise a sorted result? I prefer the solution that ``_related()`` does not sort by default. Are there use...

> it would modify the output of higher order functions like closure and tree, and deeply alter the topology of the relation trees. @ekaf can you please clarify how? Also,...

> What about just adding an optimized public related method, and leaving everything else unchanged? Interesting idea, though it risks making code less readable, having two ways of doing nearly...

I favour returning unsorted results which calling programs can trivially sort, and documenting this in docstrings (and release notes and ChangeLog). Yes, some people will see different behaviour and might...

The interface breaking update required for 3.9 was my opportunity to make @bryant1410's suggested breaking change. I went further to drop the `sort` flag. I haven't re-implemented `_related()` as an...

Let's think about new names for 'sentence_lepor' and 'corpus_lepor' which are more in keeping with NLTK practices.