django-eve-proxy transparently handles requests to the EVE API from Python code or via HTTP. This allows developers to provide a restricted or global EVE API HTTP proxy, or access the EVE API via the CachedDocument python object. See the project page for more information: http://code.google.com/p/django-eve-proxy/
1 maintainer
Metadata
1 maintainer
Release files for django-eve-proxy 0.5
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 | |
|---|---|---|---|---|
| django-eve-proxy-0.5.tar.gz | 4.1 kB | Without provenance | Details |
Release files / django-eve-proxy-0.5.tar.gz
| Download URL | django-eve-proxy-0.5.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62935d689b19204a44b6f29a798af80080b19358718c3160d6a3892319f60ed0
|
|
BLAKE2b-256 checksum How to use checksums |
68b054d961d846581c7525ff64f4e9f8c94dcf103f5186663ecea9e28b280b5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-eve-proxy 0.5
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.
