mirror of
https://github.com/explosion/spaCy.git
synced 2025-03-04 11:25:51 +03:00
* Move Entity Linker v1 component to spacy-legacy This is a follow up to #11889 that moves the component instead of removing it. In general, we never import from spacy-legacy in spaCy proper. However, to use this component, that kind of import will be necessary. I was able to test this without issues, but is this current import strategy acceptable? Or should we put the component in a registry? * Use spacy-legacy pr for CI This will need to be reverted before merging. * Add temporary step to log installed spacy-legacy version * Modify requirements.txt to trigger tests * Add comment to Python to trigger tests * TODO REVERT This is a commit with logic changes to trigger tests * Remove pipe from YAML Works locally, but possibly this is causing a quoting error or something. * Revert "TODO REVERT This is a commit with logic changes to trigger tests" This reverts commit |
||
---|---|---|
.. | ||
_edit_tree_internals | ||
_parser_internals | ||
__init__.py | ||
attribute_ruler.py | ||
dep_parser.py | ||
edit_tree_lemmatizer.py | ||
entity_linker.py | ||
entityruler.py | ||
functions.py | ||
lemmatizer.py | ||
morphologizer.pyx | ||
ner.py | ||
pipe.pxd | ||
pipe.pyi | ||
pipe.pyx | ||
sentencizer.pyx | ||
senter.pyx | ||
span_ruler.py | ||
spancat.py | ||
tagger.pyx | ||
textcat_multilabel.py | ||
textcat.py | ||
tok2vec.py | ||
trainable_pipe.pxd | ||
trainable_pipe.pyx | ||
transition_parser.pyx |