Skip to content

🕸️ Legacy architectures and other registered spaCy v3.x functions for backwards-compatibility

License

Notifications You must be signed in to change notification settings

explosion/spacy-legacy

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

60 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

spacy-legacy: Legacy functions and architectures for backwards compatibility

This package includes outdated registered functions for spaCy v3.x, for example model architectures, pipeline components and utilities. It's installed automatically as a dependency of spaCy, and allows us to provide backwards compatibility, while keeping the core library tidy and up to date. All of this happens under the hood, so you typically shouldn't have to care about this package.

tests pypi Version

How it works

Whenever a new backwards-incompatible version of a registered function is available, e.g. spacy.Tok2Vec.v1spacy.Tok2Vec.v2, the legacy version is moved to spacy-legacy, and exposed via entry points. This means that it will still be available if your config files use it, even though the core library only includes the latest version.

Legacy functions are exposed with the prefix spacy-legacy, e.g. spacy-legacy.Tok2Vec.v1. When spaCy resolves your config and a function is not available in the core library, e.g. spacy.Tok2Vec.v1, it will check if there's a legacy function available and fall back to that. You can also explicitly refer to legacy functions in your config, to indicate that a newer version is available.

Bug reports and other issues

Please use spaCy's issue tracker to report a bug, or open a new thread on the discussion board for any other issue.

About

🕸️ Legacy architectures and other registered spaCy v3.x functions for backwards-compatibility

Topics

Resources

License

Stars

Watchers

Forks