explosion/spaCy
1
1
Fork 0
mirror of https://github.com/explosion/spaCy.git synced 2025-08-04 04:10:20 +03:00
Code Issues Packages Projects Releases Wiki Activity

Add link to spacy.load docs

Browse Source
This commit is contained in:
Paul O'Leary McCann 2023-01-17 19:02:55 +09:00
parent 2c57c3fa69
commit a6f0972caf
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/docs/usage/saving-loading.mdx
View File

@ -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 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 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 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 the code that defines them before calling
`--code` argument to CLI commands works. [`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 With the [`spacy package`](/api/cli#package) command, you can provide one or
more paths to Python files containing custom registered functions using the more paths to Python files containing custom registered functions using the