Shrike: incubation for Azure ML
The shrike library is a set of Python utilities for running experiments in the
Azure Machine Learning platform (a.k.a. Azure ML). This
library contains four elements, which are:
shrike.compliant_logging: utilities for compliant logging and exception handling;shrike.pipeline: helper code for managing, validating and submitting Azure ML pipelines based on azure-ml-component (a.k.a. the Component SDK);shrike.build: helper code for packaging, building, validating, signing and registering Azure ML components.shrike.spark: utilities for running jobs, especially those leveraging Spark .NET, in HDInsight and later Synapse.
Documentation
For the full documentation of shrike with detailed examples and API reference,
please see the docs page.
For a list of problems (along with guidance and solutions) designed specifically to help you learn how to use shrike, please refer to the information in this README file (located in another GitHub repository).
Installation
The shrike library is publicly available in PyPi. There are three optional extra dependencies: pipeline, build, and dev.
The pipeline dependency is for submitting Azure ML pipelines, build is for signing and registering components,
and dev is for the development environment of shrike.
- If you are only planning on using the compliant-logging feature, please
pip installwithout any extras:
pip install shrike
- If you are planning on signing and registering components, please
pip installwith[build]:
pip install shrike[build]
- If you are planning on submitting Azure ML pipelines, please
pip installwith[pipeline]:
pip install shrike[pipeline]
- If you would like to contribute to the source code, please
pip installwith all the dependencies:
pip install shrike[pipeline,build,dev]
Alternatively, for local development, you may use the Conda environment defined in environment.yml. It pins the appropriate versions of pip, Python, and installs all shrike together with all extras as an editable package.
⚠️ If you are using a ZSH terminal, please consider adding quotes,
e.g., pip install "shrike[pipeline,build,dev]" to avoid the accidental shell expansion.
Migration from aml-build-tooling, aml-ds-pipeline-contrib, and confidential-ml-utils
If you have been using the aml-build-tooling, aml-ds-pipeline-contrib, or confidential-ml-utils libraries,
please use the migration script (migration.py) to convert your repo or files and
adopt the shrike package with one simple command:
python migraton.py --input_path PATH/TO/YOUR/REPO/OR/FILE
⚠️ This command will update files in-place. Please make a copy of your repo/file if you do not want to do so.
Need Support?
If you have any feature requests, technical questions, or find any bugs, please do not hesitate to reach out to us.
- For bug reports and feature requests, you are welcome to open an issue.
- If you are a Microsoft employee, please refer to the support page for details;
- If you are outside Microsoft, please send an email to aims-team@microsoft.com.
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
To contribute, please start by creating a self-assigned issue giving a high-level overview of what you'd like to do. Once any discussion there concludes, follow up with a PR.
Please join the security group "aml-ds-guests" on IDweb, if you have difficulty in creating a branch. When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
2 maintainers
Metadata
2 maintainers
Release files for shrike 2.0.2
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 | |
|---|---|---|---|---|
| shrike-2.0.2.tar.gz | 147.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shrike-2.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 312.2 kB
Release files / shrike-2.0.2.tar.gz
| Download URL | shrike-2.0.2.tar.gz |
|---|---|
| Size | 147.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1911a3ec665d459589e9abd5f2485a3602a8607ca48fc3916fe91ccf2356de4
|
|
BLAKE2b-256 checksum How to use checksums |
f5e79b20813a01f82ec992294d973ad056a72d2cff348dde441de9afe416290b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Release files / shrike-2.0.2-py3-none-any.whl
| Download URL | shrike-2.0.2-py3-none-any.whl |
|---|---|
| Size | 165.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
524c78f8a3de8b48b0a28295b2c33d49caa809d8e68d61e598d69ec1ab13e7eb
|
|
BLAKE2b-256 checksum How to use checksums |
199ca263efe36c6be54836c930fff371a5b0711b60736737afca278021b1cea6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Security for shrike 2.0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
