paco xander nathan

Thank you @shyamcody - we just did a relatively large refactoring of the code base, heading toward the spaCy 3.x release, and now this should be much simpler. I may...

Hi @shyamcody, In the current `main` branch, there are two new methods for the `TextRank` object: - add `get_unit_vector()` method to expose the characteristic *unit vector* - add `calc_sent_dist()` method...

Thank you @fukidzon I've reworked the code that you provided as a Colab notebook: so people can view and interact with the problem. The root issue appears to be that...

Also, there's another implied question: - Could `PyTextRank` be modified so that it does not depend on the availability of *noun chunks* ? While that's possible, and somewhat closer to...

Another issue that was mentioned: > I get tokens with POS and DEP tags, but there is nothing in doc._.phrases (doc.noun_chunks is also empty) and in nlp.pipe_names is just ['textrank']...

@fukidzon @asajatovic The points above identify two issues in the `spacy_udpipe` implementation. It might be more efficient to make a pull request on that project to resolve those issues, rather...

Thank you kindly @asajatovic, that's good to know and makes a lot of sense to use that approach. @fukidzon I can help with a syntax iterator implementation. To start I'd...

Hi @andremacola, could you help us by showing some example code about the pipeline you're building with spaCy 3.x ? We may be able to help. The code for `syntax_iterators`...

I've noticed that the pipeline extensions tend to not show up in the spaCy pipeline analysis, for example when running: ``` print("pipeline", nlp.pipe_names) nlp.analyze_pipes(pretty=True) ``` I can raise a question...

Thank you @louisguitton – Looking at this again, since `pytextrank` is assigning [custom attributes](https://spacy.io/usage/processing-pipelines) then these don't show up in the pipeline analysis.