mirror of
https://github.com/explosion/spaCy.git
synced 2024-11-14 13:47:13 +03:00
6920fb7baf
* 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 |
||
---|---|---|
.. | ||
__init__.py | ||
test_analysis.py | ||
test_annotates_on_update.py | ||
test_attributeruler.py | ||
test_edit_tree_lemmatizer.py | ||
test_entity_linker.py | ||
test_entity_ruler.py | ||
test_functions.py | ||
test_initialize.py | ||
test_lemmatizer.py | ||
test_models.py | ||
test_morphologizer.py | ||
test_pipe_factories.py | ||
test_pipe_methods.py | ||
test_sentencizer.py | ||
test_senter.py | ||
test_span_ruler.py | ||
test_spancat.py | ||
test_tagger.py | ||
test_textcat.py | ||
test_tok2vec.py |