Change Log
1.0.23 (July 11, 2014)
Added a generic customer for parsing customers and address.
Implemented GrandTotat, Customer and Address for GetOrderDetailsRequest.
Added parse_cart_item function to be used in Cart and in a TicketOrder.
Implemented OrderItems, they are supposed to be different to cart items.
1.0.22 (July 11, 2014)
Fixed the way order details is parsed, it wasn’t being parsed at correct level.
1.0.21 (July 11, 2014)
Fixed order_id in GetOrderDetailsRequest implementation
1.0.20 (July 3, 2014)
Event dates are parsed accordingly its timezone.
1.0.19 (July 3, 2014)
If a date comes empty in purchase client, it will be converted to None.
Changed the parse order for dates received in search client.
Implemented last_response in clients.
Implemented get_zone_list in WanticketsSearchClient.
Implemented Search -> getPromerList.
Metadata
Release files for pywantickets 1.0.24
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 | |
|---|---|---|---|---|
| pywantickets-1.0.24.tar.gz | 11.2 kB | Without provenance | Details |
Release files / pywantickets-1.0.24.tar.gz
| Download URL | pywantickets-1.0.24.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31671e883141495fdef8e36c720a790120f6b4a0e17cf2876ebf33d8f2cf7145
|
|
BLAKE2b-256 checksum How to use checksums |
6320ab44aa2ff0f3e26b3dff5bbc152c80efb10d38c8b43ec3a72eb9e6736e90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pywantickets 1.0.24
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.