This release is a pre-release and may not be stable for production use.
FlagCloud
Python connectivity tools for cloud platforms. This alpha implements same-origin JSON reads with optional bearer authentication, bounded responses, and explicit timeout handling.
python -m pip install flagcloud==0.1.0a1
from getpass import getpass
from flagcloud import Client
# Replace both the origin and API path with your service's documented values.
with Client('https://your-cloud.example', token=getpass('Cloud token: ')) as cloud:
resources = cloud.get_json('/your-documented-resource-path', params={'limit': '10'})
print(resources)
No platform-specific endpoint is assumed. This release does not yet implement a dedicated Liangzhi Cloud authentication, workspace, scheduling, or task API. It can read existing HTTP JSON endpoints today, without publishing any private platform implementation.
Behavior
Client(base_url, token=None, timeout=30, max_response_bytes=8388608)accepts an HTTPS origin. HTTP is allowed only for loopback development.get_json(path, params=None)performs one GET and returns the decoded JSON. Pass query values throughparams; paths cannot select another origin.- Bearer tokens stay in memory. Exiting the context or calling
close()removes the token from the client; it does not revoke it at the service. - Redirects and automatic retries are disabled. This client has no task-submission or arbitrary POST method.
CloudError.status_coderecords HTTP failures. Exceptions omit response bodies and transport error details; no client logging is performed.- Timeout is per socket operation, not a whole-workflow deadline. Responses exceeding the configured byte limit and invalid JSON are rejected.
No third-party runtime dependencies; Python 3.10+. Python 3.12 is the tested baseline. Tests use local HTTP fixtures, not a live cloud deployment. Client instances are not intended for concurrent use. APIs may change during alpha.
Development
python -m pip install -e .
python -m unittest discover -s tests -v
Apache-2.0 licensed.
Metadata
Release files for flagcloud 0.1.0a1
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 |
|---|---|---|---|---|
| flagcloud-0.1.0a1.tar.gz | 9.4 kB | Without provenance | Details for flagcloud-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flagcloud-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for flagcloud-0.1.0a1-py3-none-any.whl |
Total release size: 18.3 kB
Release files / flagcloud-0.1.0a1.tar.gz
| Download URL | flagcloud-0.1.0a1.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8112d988bbc4117d4213b416a6d24bc22e2d6d735fab5abae07acecc59a7e8e7
|
|
BLAKE2b-256 checksum How to use checksums |
fef3e76e60fce61e07f3bb71a07e970297df6488c6f55fa124eaf5504d19e8df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.14
|
Release files / flagcloud-0.1.0a1-py3-none-any.whl
| Download URL | flagcloud-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e77562dfdaf9a4142f10382125e076067c1099672acd75683dd56558d207263a
|
|
BLAKE2b-256 checksum How to use checksums |
5fdf43342507754cc1cc9ba5a5d35891a10186f56f15d0511c3a763d6b4b27be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.14
|
Security for flagcloud 0.1.0a1
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.