This is a simple caching handler for urllib2.
Usage
Either use the build_opener function which takes the path to the cache folder and returns an OpenerDirector instance. You can then use it’s open method to open urls normally. If the file was already downloaded, then it will be taken from the cache.
You can also use the CachedHandler wherever it’s useful within urllib2. This also takes the path to cache folder as an argument of the constructor.
Be aware that the caching is very simple. It detects incomplete downloads but doesn’t take any caching headers into account. To invalidate the cache you have to delete the files in the cache folder.
Changelog
1.0.1 - 2008-07-23
Fixed packaging. [fschulze]
1.0 - 2008-07-22
Initial release. [fschulze]
1 maintainer
Metadata
1 maintainer
Release files for urllibcache 1.0.1
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 | |
|---|---|---|---|---|
| urllibcache-1.0.1.tar.gz | 2.3 kB | Without provenance | Details |
Release files / urllibcache-1.0.1.tar.gz
| Download URL | urllibcache-1.0.1.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23979936958b5c0e4c312c0ad720c39db027dde042c1e29b96c104c9ee8ded5d
|
|
BLAKE2b-256 checksum How to use checksums |
02666b663ef01bc5b7d582b249deef8a0e08588db1d912b62ba1889017d11778
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for urllibcache 1.0.1
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.
