Launchpy
Python wrapper for the Adobe Launch API.
This module is named launchpy.
Current version: 0.5.2. This version fixes GET retries and adds automatic HTTP 429 retries across all five connector methods. See the 0.5.2 release notes for details.
Installation
You can install the module by realising the following pip command:
pip install launchpy
You can access the version of the module that you run via the following attribute:
launchpy.__version__
Content of the module
This module is built around 7 main parts:
- Helping functions Core Components
- Admin instantiating functions Admin Class
- Managing properties Property Class
- Managing Publishing Cycle Library Class
- Translator functionationality Translator Class
- Synchronizer Synchronizer Class
- Command Line Interface CLI
Get Started
A get started guide has been created to explain the different functionality. You can find a more detail description functionalities at datanalyst.info.
Main documentation
Most of the documentation has been imported from the datanalyst website here.
Release information
You can find release information here.
Proxy support
Pass a proxy URL to launchpy.configure(...), or add "proxy" to
your JSON configuration file. The same proxy serves both HTTP and HTTPS.
Proxy settings apply to OAuth authentication,
API requests, and asynchronous property exports, with separate settings per
organization.
launchpy.configure(
org_id="your-org@AdobeOrg",
client_id="your-client-id",
secret="your-secret",
scopes="your-scopes",
proxy="http://proxy.example.com:8080",
)
The CLI accepts --proxy URL at startup and in the interactive config
command. An explicit CLI proxy overrides the file setting.
Without an explicit proxy, existing environment-based proxy behavior is unchanged.
See the Python and JSON examples
and CLI examples.
HTTP retries
The AdobeRequest connector always retries HTTP 429 responses for GET, POST,
PUT, PATCH, and DELETE, even when their body is not JSON or retry=0.
Rate-limit retries have no attempt limit and do not consume the configured
retry budget. A request can therefore keep waiting while the API remains
rate limited; it can be interrupted normally.
The connector
honors Retry-After in seconds or HTTP-date format; absent or invalid values
use exponential backoff starting at 45 seconds and capped at 300 seconds.
The JSON-returning methods also always retry Adobe error code 429050.
The retry setting is reserved for other retryable errors: currently, GET
responses that cannot be decoded as JSON. It specifies the number of
additional attempts, with a default of 0. Set
property.connector.retry = 3 or pass retry=3 to a connector method to
override this budget; neither setting limits rate-limit retries.
Successful return values are unchanged: DELETE returns the HTTP status code, while the other methods return decoded JSON. GET also retries invalid JSON responses with a 30-second delay. Invalid JSON from write operations and network exceptions do not trigger retries, to avoid replaying writes that may already have succeeded. This policy applies to the five connector methods, not the separate OAuth token request or async property-extraction requests.
Metadata
Release files for launchpy 0.5.4.post1
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 |
|---|---|---|---|---|
| launchpy-0.5.4.post1.tar.gz | 113.2 kB | Without provenance | Details for launchpy-0.5.4.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| launchpy-0.5.4.post1-py3-none-any.whl | Python 3 | none | any | Details for launchpy-0.5.4.post1-py3-none-any.whl |
Total release size: 187.9 kB
Release files / launchpy-0.5.4.post1.tar.gz
| Download URL | launchpy-0.5.4.post1.tar.gz |
|---|---|
| Size | 113.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf04ce775da7bd64d06dfa20b68c2e690b55e4ae1b99a720ef947c06c46dc0b7
|
|
BLAKE2b-256 checksum How to use checksums |
f9592894f495d5795f5099f78f7f9c9785958e05fb5b2fc7fbcd47d082cb60dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / launchpy-0.5.4.post1-py3-none-any.whl
| Download URL | launchpy-0.5.4.post1-py3-none-any.whl |
|---|---|
| Size | 74.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2516f67a0e44a6d0f134e6df9dc4861de7c1eb0aea5955db224c75244c11a444
|
|
BLAKE2b-256 checksum How to use checksums |
f8d00235ae05f1fc53c0df778dc2385b1a3a40d9c594602e0f34775139181fe7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for launchpy 0.5.4.post1
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.