This release is a pre-release and may not be stable for production use.
ascribe SPOOL API Python Wrapper
ascribe ownership REST API Python wrapper.
Installation
pip install ascribeExample: Registering a Piece
>>> from ascribe import AscribeWrapper
>>> ascribe_wrapper = AscribeWrapper('your-token')
>>> piece = {
'file_url': 'https://s3.eu-central-1.amazonaws.com/bucket/img.jpg',
'artist_name': 'mystery',
'title': 'universe',
}
>>> ascribe_wrapper.create_piece(piece)
{'piece': {
'artist_name': 'mystery',
'bitcoin_id': 'bitcoin-id',
'date_created': '2015-01-01',
'datetime_registered': '2015-11-28T20:42:19.917896Z',
'license_type': {
'code': 'default',
'name': 'All rights reserved',
'organization': 'ascribe',
'url': 'https://www.ascribe.io/faq/#legals'
},
'title': 'universe',
'user_registered': 'mystery'
...
...
}}Documentation
1 maintainer
Metadata
1 maintainer
Release files for ascribe 0.0.9.dev1
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 | |
|---|---|---|---|---|
| ascribe-0.0.9.dev1.tar.gz | 3.2 kB | Without provenance | Details |
Release files / ascribe-0.0.9.dev1.tar.gz
| Download URL | ascribe-0.0.9.dev1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7a295e962b4c8733c425e712c09df5e5ebb85b4b9043c4fc4e0e4146976dc942
|
|
BLAKE2b-256 checksum How to use checksums |
2b93fe20422bf5cef3eb465d947ee49f4f4eadd247877c00a4d2caa75c67e082
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ascribe 0.0.9.dev1
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.
