Python 3 client for the Real Estate Transaction Standard (RETS) Version 1.7.2
1 maintainer
Metadata
1 maintainer
Release files for rets-python 0.4.12
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 | |
|---|---|---|---|---|
| rets_python-0.4.12.tar.gz | 17.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rets_python-0.4.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.8 kB
Release files / rets_python-0.4.12.tar.gz
| Download URL | rets_python-0.4.12.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d42dd5dbf26d65b77c571cab7887447bc5e199d0b0abaa78767e5a0e9ff37953
|
|
BLAKE2b-256 checksum How to use checksums |
500d2f4561af0b74f53c99630fcb5ceea1995463f19aa639a26235d760f188d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Release files / rets_python-0.4.12-py3-none-any.whl
| Download URL | rets_python-0.4.12-py3-none-any.whl |
|---|---|
| Size | 20.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cfa23005cb887d87b77d5ba65200ede1eb740965d8692f15cfaa7e53aeab4ae9
|
|
BLAKE2b-256 checksum How to use checksums |
57881afebca7c2bfeeb404d0b536c1ee61d3cc6a0dea79c37fa86b94249ca26f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Security for rets-python 0.4.12
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.
