Launch Python Client
██╗ █████╗ ██╗ ██╗███╗ ██╗ ██████╗██╗ ██╗
██║ ██╔══██╗██║ ██║████╗ ██║██╔════╝██║ ██║
██║ ███████║██║ ██║██╔██╗ ██║██║ ███████║
██║ ██╔══██║██║ ██║██║╚██╗██║██║ ██╔══██║
███████╗██║ ██║╚██████╔╝██║ ╚████║╚██████╗██║ ██║
╚══════╝╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═══╝ ╚═════╝╚═╝ ╚═╝
Moving an ML model from experiment to production requires significant engineering lift. Scale Launch provides ML engineers a simple Python interface for turning a local code snippet into a production service. A ML engineer needs to call a few functions from Scale's SDK, which quickly spins up a production-ready service. The service efficiently utilizes compute resources and automatically scales according to traffic.
Latest API/SDK reference can be found here.
Deploying your model via Scale Launch
Central to Scale Launch are the notions of a ModelBundle and a ModelEndpoint.
A ModelBundle consists of a trained model as well as the surrounding preprocessing and postprocessing code.
A ModelEndpoint is the compute layer that takes in a ModelBundle, and is able to carry out inference requests
by using the ModelBundle to carry out predictions. The ModelEndpoint also knows infrastructure-level details,
such as how many GPUs are needed, what type they are, how much memory, etc. The ModelEndpoint automatically handles
infrastructure level details such as autoscaling and task queueing.
Steps to deploy your model via Scale Launch:
-
First, you create and upload a
ModelBundle. -
Then, you create a
ModelEndpoint. -
Lastly, you make requests to the
ModelEndpoint.
TODO: link some example colab notebook
For Developers
Clone from github and install as editable
git clone git@github.com:scaleapi/launch-python-client.git
cd launch-python-client
pip3 install poetry
poetry install
Please install the pre-commit hooks by running the following command:
poetry run pre-commit install
The tests can be run with:
poetry run pytest
Documentation
Updating documentation: We use Sphinx to autogenerate our API Reference from docstrings.
To test your local docstring changes, run the following commands from the repository's root directory:
poetry shell
cd src_docs
sphinx-autobuild . ../docs --watch ../launch
sphinx-autobuild will spin up a server on localhost (port 8000 by default) that will watch for and automatically rebuild a version of the API reference based on your local docstring changes.
Metadata
Release files for scale-launch 0.3.3
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 | Actions |
|---|---|---|---|---|
| scale-launch-0.3.3.tar.gz | 51.7 kB | Without provenance | Details for scale-launch-0.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scale_launch-0.3.3-py3-none-any.whl | Python 3 | none | any | Details for scale_launch-0.3.3-py3-none-any.whl |
Total release size: 116.1 kB
Release files / scale-launch-0.3.3.tar.gz
| Download URL | scale-launch-0.3.3.tar.gz |
|---|---|
| Size | 51.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc74b8b8c578102a6011c059e985653bd09e116f63d2c6faa1567cacebb499db
|
|
BLAKE2b-256 checksum How to use checksums |
42ad02df5c8875fbbecedff6a779b724b481a223b02f6933edd5bc90039a8651
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.7 CPython/3.9.13 Darwin/20.6.0
|
Release files / scale_launch-0.3.3-py3-none-any.whl
| Download URL | scale_launch-0.3.3-py3-none-any.whl |
|---|---|
| Size | 64.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
830c2bd22129d33f897167ef90f9777c061dea0b66dac64a86fcb451bfabbb5e
|
|
BLAKE2b-256 checksum How to use checksums |
f7b21de375aa1e7f1d5d55e57abecdd6350cf63341660cee529966e57eb243f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.7 CPython/3.9.13 Darwin/20.6.0
|
Security for scale-launch 0.3.3
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.