Weasel: A small and easy workflow system
Weasel lets you manage and share end-to-end workflows for
different use cases and domains, and orchestrate training, packaging and
serving your custom pipelines. You can start off by cloning a pre-defined
project template, adjust it to fit your needs, load in your data, train a
pipeline, export it as a Python package, upload your outputs to a remote storage
and share your results with your team. Weasel can be used via the
weasel command and we provide templates in our
projects repo.
💡 Example: Get started with a project template
The easiest way to get started is to clone a project template and run it – for example, this end-to-end template that lets you train a spaCy part-of-speech tagger and dependency parser on a Universal Dependencies treebank.
python -m weasel clone pipelines/tagger_parser_ud
Note
Our
projectsrepo includes various project templates for different NLP tasks, models, workflows and integrations that you can clone and run. The easiest way to get started is to pick a template, clone it and start modifying it!
📕 Documentation
Get started with the documentation:
- Learn how to create a Weasel workflow
- Working with directory and assets
- Running custom scripts
- Using remote storage
- Weasel integrations
- Command line interface description
Migrating from spaCy Projects
Weasel is a standalone replacement for spaCy Projects. There are a few backward incompatibilities that you should be aware of:
- The
SPACY_CONFIG_OVERRIDESenvironment variable is no longer checked. You can set configuration overrides usingWEASEL_CONFIG_OVERRIDES. - Support for the
spacy_versionconfiguration key has been dropped. - Support for the
check_requirementsconfiguration key has been dropped. - Support for
SPACY_PROJECT_USE_GIT_VERSIONenvironment variable has been dropped. - Error codes are now Weasel-specific, and do not follow spaCy error codes.
Weasel checks for the first three incompatibilities and will issue a warning if you're using it with spaCy-specific configuration options.
1 maintainer
Metadata
1 maintainer
Release files for weasel 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| weasel-1.0.1.tar.gz | 39.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| weasel-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 90.1 kB
Release files / weasel-1.0.1.tar.gz
| Download URL | weasel-1.0.1.tar.gz |
|---|---|
| Size | 39.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca5dbfd24002dd85bd8a73a7f02d2471744c1b1a64d25698e05bb587a099a43e
|
|
BLAKE2b-256 checksum How to use checksums |
d7bf490fc13b28ad51b6c5c36d2abae1b9b64101d24ec7cb2aefa7d6504fd5cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logRelease files / weasel-1.0.1-py3-none-any.whl
| Download URL | weasel-1.0.1-py3-none-any.whl |
|---|---|
| Size | 51.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7d37540e4b5e53c783bae292d2e5dfaa8f6054160cec633e0782afce89c504d
|
|
BLAKE2b-256 checksum How to use checksums |
896653b57003567d506e2f0f7b9859a4d2e6e748d3f0ed8f494b98f684d6696d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logSecurity for weasel 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for weasel-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
