LaterPay Python client.
If you’re using Django then you probably want to look at django-laterpay
Installation
$ pip install laterpay-client
Usage
Development
Release Checklist
Install twine with $ pipsi install twine
Determine next version number from the CHANGELOG.md (ensuring we follow SemVer)
git flow release start $newver
Ensure CHANGELOG.md is representative
Update the CHANGELOG.md with the new version
Update the version in setup.py
Update trove classifiers in setup.py
git flow release finish $newver
git push --tags origin develop master
python setup.py sdist bdist_wheel
twine upload dist/laterpay*$newver* or optionally, for signed releases twine upload -s ...
Bump version in setup.py to next likely version as Alpha 1 (e.g. 5.1.0a1)
Alter trove classifiers in setup.py
Add likely new version to CHANGELOG.md
Metadata
Release files for laterpay-client 5.9.0
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 | |
|---|---|---|---|---|
| laterpay-client-5.9.0.tar.gz | 9.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| laterpay_client-5.9.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 22.7 kB
Release files / laterpay-client-5.9.0.tar.gz
| Download URL | laterpay-client-5.9.0.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1891ddf031ee9de9e4f548290da9bd9426ee32e31ceb1b85381f0b99eb7a863f
|
|
BLAKE2b-256 checksum How to use checksums |
425ad112ba3d3b53caa5a6bcff82c28418bd86ba57ca9996f2db7c5237fca2a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / laterpay_client-5.9.0-py2.py3-none-any.whl
| Download URL | laterpay_client-5.9.0-py2.py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3a829dd70091e169cd68b7143ef634eebe062e3aa2cbed501b3f80a87d0a0ea1
|
|
BLAKE2b-256 checksum How to use checksums |
bd2d423cc66cf85a643b8559dad932ff7c03e2458855a2f96b82b9eedaf744a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for laterpay-client 5.9.0
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.