mirror of
https://github.com/explosion/spaCy.git
synced 2024-12-26 01:46:28 +03:00
Fix typo in saving and loading usage docs
This commit is contained in:
parent
3aa57ce6c9
commit
cc71ec901f
|
@ -299,9 +299,10 @@ installed in the same environment – that's it.
|
|||
|
||||
When you load a pipeline, spaCy will generally use its `config.cfg` to set up
|
||||
the language class and construct the pipeline. The pipeline is specified as a
|
||||
list of strings, e.g. `pipeline = ["tagger", "paser", "ner"]`. For each of those
|
||||
strings, spaCy will call `nlp.add_pipe` and look up the name in all factories
|
||||
defined by the decorators [`@Language.component`](/api/language#component) and
|
||||
list of strings, e.g. `pipeline = ["tagger", "parser", "ner"]`. For each of
|
||||
those strings, spaCy will call `nlp.add_pipe` and look up the name in all
|
||||
factories defined by the decorators
|
||||
[`@Language.component`](/api/language#component) and
|
||||
[`@Language.factory`](/api/language#factory). This means that you have to import
|
||||
your custom components _before_ loading the pipeline.
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user