Determine if this cached response is expired

Indicate whether or not requests-cache is currently installed

Check documentation for dead links

Run linters and code formatters via pre-commit

Auto-build docs with live reload in browser. Add `--open` to also open the browser after starting.

The lock used by the cache.

The lock used by the cache.

Make a converter that uses Decimals instead of floats to represent timedelta objects

Fixture for combining requests-cache with requests-mock. This will behave the same as a CachedSession, except it will make mock requests for ``moc

Fixture that provides a session with mocked URLs and responses based on cache data

Fixture that provides a CachedSession that will make mock requests where it would normally make real requests

Returns a PreparedRequest for the next request in a redirect chain, if there is one.

Monkey-patch the automodapi extension to exclude imported members: https://github.com/astropy/sphinx-automodapi/blob/main/sphinx_automodapi/automo

Get absolute file paths to all cached responses

No-op for compatibility

Set a new expiration for this response

Create or update a TTL index. Notes: * This will have no effect if TTL is already set * To overwrite an existing TTL index, use ``ove

Settings that affect cache behavior

Run some additional steps after the Sphinx builder is initialized

Return the size of the database, in bytes

Return the size of the database, in bytes

Get the size of the response body in bytes

Get LRU entries in sorted order, by either ``access_time`` or ``size``

Get cached responses, with sorting and other query options. Args: key: Key to sort by; either 'expires', 'size', or 'key'

Template function to get an accurate signature for the builtin :py:func:`sqlite3.connect`

Run concurrency tests with a higher stress test multiplier

Get a unique tempfile path

Get a CachedSession using a temporary SQLite db

Run tests in a separate virtualenv per python version

Test all relevant combinations of methods and data fields. Requests with different request params, data, or json should be cached under different

Test all relevant combinations of methods X data fields X serializers

Test all relevant combinations of methods X data fields. Requests with different request params, data, or json should be cached under differen

Test all relevant combinations of methods and data fields. Requests with different request params, data, or json should not be cached under differ

Test all relevant combinations of methods and data fields. Requests with ignored params should have those values redacted from the cached response

Test all relevant combinations of response formats X serializers

Test with decode_content=True for text-based serialization formats

The session always_revalidate option should send a conditional request, if possible

Test basic dict methods with multiple cache instances: ``getitem, setitem, delitem, len, contains``

File size should be aligned with the block on the file system, and be taken into account when adding, replacing, and deleting items.

Check boolean conversion.

When deleting more items than SQLite can handle in a single statement, it should be chunked into multiple smaller statements

Just make sure bulk_delete doesn't do anything unexpected if no keys are provided

Test cache headers for both requests and responses. The `/cache/{seconds}` endpoint returns Cache-Control headers, which should be used unless

If there is an error while fetching a cached response, a new one should be fetched

The cache_key attribute should be available on responses returned from all mapping/collection methods

CattrStage should be compatible with BaseConverter, which doesn't support the omit_if_default keyword arg.

When a corrupted cache prevents a normal DROP TABLE, clear() should still succeed

If clear is called without a cache installed, it should just fail silently

By default, backend connections should be closed when the session closes

With autoclose=False, backend connections should NOT be closed when the session closes

On GitHub runners, sometimes the MongoDB container is not ready yet by the time this, runs, so some retries are added here.

Run multithreaded and multiprocess stress tests for each backend. The number of workers (thread/processes), iterations, and requests per itera

Test a large number of concurrent write operations for each backend

Test behavior of ETag and Last-Modified headers and 304 responses. When a cached response contains one of these headers, corresponding reques

Test that revalidation attempt with 304 responses causes stale entry to become fresh again considering Cache-Control header of the 304 respons

Test response headers that can initiate revalidation before a cached response expires

A spot check to make sure optional connection kwargs gets passed to connection; except for isolation_level, which is ignored

A spot check to make sure optional connection kwargs gets passed to connection

A spot check to make sure optional connection kwargs gets passed to connection

A spot check to make sure optional connection kwargs gets passed to connection

A spot check to make sure optional connection kwargs get passed to connection