YellowDog SDK (Python)
The YellowDog SDK allows you to integrate the YellowDog Platform into your Python applications.
Usage
Please refer to the full documentation.
Advanced
Building From Source
If you wish to modify the SDK, you can build it from source. You must have Python 3.15 installed:
./scripts/setup
Pycharm may then be configured by adding .tox/dev/bin/python as the interpreter.
Debugging
When debugging the SDK via Pycharm, Pycharm will offer to install the CPython extensions to speed up debugging.
In order for this to work on Ubuntu, you need to first have the dev package for the version of Python you are debugging against.
For example:
sudo apt-get install python3.11-dev
Testing Against Multiple Python Versions
# Add the deadsnakes PPA
sudo add-apt-repository ppa:deadsnakes/ppa
# Update package indexes
sudo apt-get update
# Install all tested versions of Python
sudo apt-get install python3.11 python3.12 python3.13 python3.14 python3.15
Assuming you have already run the setup script and installed tox, you can then run all tests:
./scripts/test
Metadata
Release files for yellowdog-sdk 15.9.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| yellowdog_sdk-15.9.1-py3-none-any.whl | Python 3 | none | any | Details for yellowdog_sdk-15.9.1-py3-none-any.whl |
Release files / yellowdog_sdk-15.9.1-py3-none-any.whl
| Download URL | yellowdog_sdk-15.9.1-py3-none-any.whl |
|---|---|
| Size | 246.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49eb987e398da461fc47661859127750d490fd9490db2f894ccd1fd8120d1576
|
|
BLAKE2b-256 checksum How to use checksums |
e521ebfcfb5ce2f208939e5cfef4ed93050a5419be84d2b00f1645f3593291f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for yellowdog-sdk 15.9.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.
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.