mirror of
https://github.com/explosion/spaCy.git
synced 2025-04-21 17:41:59 +03:00
Add info to sections
This commit is contained in:
parent
ce258670b7
commit
3db9d29393
|
@ -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">
|
||||
|
||||
|
|
|
@ -758,6 +758,14 @@ any custom architectures, functions or
|
|||
your pipeline and registered when it's loaded. See the documentation on
|
||||
[saving and loading pipelines](/usage/saving-loading#models-custom) for details.
|
||||
|
||||
<Infobox variant="warning">
|
||||
|
||||
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>
|
||||
|
||||
#### Example: Modifying the nlp object {id="custom-code-nlp-callbacks"}
|
||||
|
||||
For many use cases, you don't necessarily want to implement the whole `Language`
|
||||
|
|
Loading…
Reference in New Issue
Block a user