from lightweight_b2.core.b2_client import B2Clientfrom ctypes import pythonapi
___ __ __ _ __ __ __ ___
/ (_)___ _/ /_ / /__ _____ (_)___ _/ /_ / /_ / /_ |__ \
/ / / __ `/ __ \/ __/ | /| / / _ \/ / __ `/ __ \/ __/ / __ \__/ /
/ / / /_/ / / / / /_ | |/ |/ / __/ / /_/ / / / / /_ / /_/ / __/
/_/_/\__, /_/ /_/\__/ |__/|__/\___/_/\__, /_/ /_/\__/ /_.___/____/
/____/ /____/
lightweight-b2
Ultra-lightweight B2 client. Memory leakage not implemented yet (unlike boto3)
pip install lightweight-b2
Supports:
- sending existing files
- sending string as zipped json (data sinks)
- Operates within a session refreshed every four hours; be sure to shut down the client when you’re done.
Usage
Create StorageConnectionParameters:from lightweight_b2 import StorageConnectionParameters
storage_connection_parameters = StorageConnectionParameters(
backblaze_access_key_id='access_key_id',
backblaze_secret_access_key='secret_access_key',
backblaze_endpoint_url='endpoint_url',
backblaze_bucket_name='bucket_name'
)
Or just put em into the .env file. Load the .env using load_dotenv()
StorageConnectionParameters() will read all of parameters in format:
BACKBLAZE_ACCESS_KEY_ID=
BACKBLAZE_SECRET_ACCESS_KEY=
BACKBLAZE_ENDPOINT_URL=
BACKBLAZE_BUCKET_NAME=
or
AZURE_BLOB_PARAMETERS_WITH_KEY=
AZURE_CONTAINER_NAME=
then:
load_dotenv(env_path)
storage_connection_parameters = StorageConnectionParameters()
b2_client = B2Client(storage_connection_parameters)
b2_client.upload_existing_file(file_path='C:/JohnnySins/Documents/SomeFile.csv')
b2_client.upload_zipped_jsoned_string(
data='{some_sophisticated_data....}',
file_name='some_csv_name.csv'
)
b2_client.shutdown()
Sample Main
And the final sample main.py would look like:from lightweight_b2 import B2Client, StorageConnectionParameters
if __name__ == '__main__ ':
storage_connection_parameters = StorageConnectionParameters(
backblaze_access_key_id='access_key_id',
backblaze_secret_access_key='secret_access_key',
backblaze_endpoint_url='endpoint_url',
backblaze_bucket_name='bucket_name'
)
"""
Or just put em into the .env file. Load the .env using:
load_dotenv(env_path)
and then read it using:
storage_connection_parameters = StorageConnectionParameters()
"""
b2_client = B2Client(storage_connection_parameters)
b2_client.upload_existing_file(file_path='C:/JohnnySins/Documents/SomeFile.csv')
b2_client.upload_zipped_jsoned_string(
data='some_sophisticated_data....',
file_name='some_csv_name.csv'
)
b2_client.shutdown()
Metadata
Release files for lightweight-b2 0.0.1
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 | |
|---|---|---|---|---|
| lightweight_b2-0.0.1.tar.gz | 6.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lightweight_b2-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.5 kB
Release files / lightweight_b2-0.0.1.tar.gz
| Download URL | lightweight_b2-0.0.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f086201129982b50b26ae87ffeae114dbf54bd6136cad3917e3eb7ed627bb489
|
|
BLAKE2b-256 checksum How to use checksums |
74984976dfa330fc13fee16048ea169c27610dae68c7e98bf5bf85d41279d9fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.4
|
Release files / lightweight_b2-0.0.1-py3-none-any.whl
| Download URL | lightweight_b2-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5695897444ddbdccca9cee01558b96e7cea3598bf5fc2bfe53723f51a522eb45
|
|
BLAKE2b-256 checksum How to use checksums |
efc09fcdf6f9fc6e00e1ae43819737831c73122062d8c7661de848fbcc4a8891
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.4
|
Security for lightweight-b2 0.0.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.