mirror of
https://github.com/explosion/spaCy.git
synced 2025-08-04 04:10:20 +03:00
Add link to spacy.load docs
This commit is contained in:
parent
2c57c3fa69
commit
a6f0972caf
|
@ -686,8 +686,9 @@ architectures or other [code](/usage/training#custom-code), those functions need
|
|||
to be registered **before** your pipeline is loaded. Otherwise, spaCy won't know
|
||||
how to create the objects referenced in the config. If you're loading your own
|
||||
pipeline in Python, you can make custom components available just by importing
|
||||
the code that defines them before calling `spacy.load`. This is also how the
|
||||
`--code` argument to CLI commands works.
|
||||
the code that defines them before calling
|
||||
[`spacy.load`](/api/top-level#spacy.load). This is also how the `--code`
|
||||
argument to CLI commands works.
|
||||
|
||||
With the [`spacy package`](/api/cli#package) command, you can provide one or
|
||||
more paths to Python files containing custom registered functions using the
|
||||
|
|
Loading…
Reference in New Issue
Block a user