stellar-py
==========
Python client library for Stellar
[](http://badge.fury.io/py/stellar-py)
# Generating keys
```python
account, secret = generate_keypair(password=None)
```
# Signing and submitting transactions
At the highest level of abstraction there are functions like these,
```python
send_payment(secret, account, destination, amount)
set_regular_key(secret, account, regular_key)
```
Lower down the operations are separated for easy offline usage,
where you create the transaction json object, sign the transaction,
and then submit it as separate steps.
```python
tc_json = get_payment_tx_json(account, destination, amount)
tx_blob = sign_transaction(secret, tx_json)
res, msg = submit_transaction(tx_blob)
```
At an even lower level, you can create your own transaction json object,
and have stellar-py take over from there.
```python
import stellar
tx_json = {
'TransactionType': 'Payment',
'Account': account,
'Amount': amount,
'Destination': dest,
}
stellar.complete_transaction_fields(tx_json)
tx_blob = stellar.sign_transaction(secret, tx_json)
stellar.submit_transaction(tx_blob)
```
# Installation
Only tested on Python 2.7
In most cases, this is enough to install:
$ pip install stellar-py
If not, then you might need these too:
$ apt-get install python-pip
$ apt-get install python-dev
==========
Python client library for Stellar
[](http://badge.fury.io/py/stellar-py)
# Generating keys
```python
account, secret = generate_keypair(password=None)
```
# Signing and submitting transactions
At the highest level of abstraction there are functions like these,
```python
send_payment(secret, account, destination, amount)
set_regular_key(secret, account, regular_key)
```
Lower down the operations are separated for easy offline usage,
where you create the transaction json object, sign the transaction,
and then submit it as separate steps.
```python
tc_json = get_payment_tx_json(account, destination, amount)
tx_blob = sign_transaction(secret, tx_json)
res, msg = submit_transaction(tx_blob)
```
At an even lower level, you can create your own transaction json object,
and have stellar-py take over from there.
```python
import stellar
tx_json = {
'TransactionType': 'Payment',
'Account': account,
'Amount': amount,
'Destination': dest,
}
stellar.complete_transaction_fields(tx_json)
tx_blob = stellar.sign_transaction(secret, tx_json)
stellar.submit_transaction(tx_blob)
```
# Installation
Only tested on Python 2.7
In most cases, this is enough to install:
$ pip install stellar-py
If not, then you might need these too:
$ apt-get install python-pip
$ apt-get install python-dev
Metadata
Release files for stellar-py 0.1.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 | |
|---|---|---|---|---|
| stellar-py-0.1.1.tar.gz | 6.5 kB | Without provenance | Details |
Release files / stellar-py-0.1.1.tar.gz
| Download URL | stellar-py-0.1.1.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fed3095d3e0addb550209abc5cb51d030dd5d8a12ffc4db85139fe3f712530c
|
|
BLAKE2b-256 checksum How to use checksums |
11d0d958d3f5ce4199f5e7c24744d7aef1ea0c4c1b21d96ffa2c54d32d7ce27c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for stellar-py 0.1.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.