mirror of
https://github.com/explosion/spaCy.git
synced 2025-04-21 17:41:59 +03:00
link to spacy load and mention difference
This commit is contained in:
parent
f21d12bbff
commit
1e820aceb4
|
@ -25,7 +25,10 @@ and call the package's own `load()` method. If a pipeline is loaded from a path,
|
|||
spaCy will assume it's a data directory, load its
|
||||
[`config.cfg`](/api/data-formats#config) and use the language and pipeline
|
||||
information to construct the `Language` class. The data will be loaded in via
|
||||
[`Language.from_disk`](/api/language#from_disk).
|
||||
[`Language.from_disk`](/api/language#from_disk). Loading a pipeline from a
|
||||
package will also import any custom code, if present, whereas loading from a
|
||||
directory does not. For these cases, you need to manually import your custom
|
||||
code.
|
||||
|
||||
<Infobox variant="warning" title="Changed in v3.0">
|
||||
|
||||
|
|
|
@ -760,9 +760,9 @@ your pipeline and registered when it's loaded. See the documentation on
|
|||
|
||||
<Infobox variant="warning">
|
||||
|
||||
Please note that unpackaged models produced by `spacy train` do **not include
|
||||
any custom code**, you need to import the code in your script before loading
|
||||
unpackaged models.
|
||||
Note that unpackaged models produced by `spacy train` do **not include custom
|
||||
code**, you need to import the code to your script before loading in unpackaged
|
||||
models. For more details, see [`spacy.load`](/api/top-level#spacy.load).
|
||||
|
||||
</Infobox>
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user