From a6f0972cafc3753049635ec47d334bcc97e58a67 Mon Sep 17 00:00:00 2001 From: Paul O'Leary McCann Date: Tue, 17 Jan 2023 19:02:55 +0900 Subject: [PATCH] Add link to spacy.load docs --- website/docs/usage/saving-loading.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/docs/usage/saving-loading.mdx b/website/docs/usage/saving-loading.mdx index e4f4c8f9e..e0daebe35 100644 --- a/website/docs/usage/saving-loading.mdx +++ b/website/docs/usage/saving-loading.mdx @@ -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