Source: python-requests-cache
Section: python
Maintainer: Sandro Tosi <morph@debian.org>
Build-Depends: debhelper-compat (= 14),
               dh-sequence-python3,
               dh-sequence-single-binary,
               pybuild-plugin-pyproject,
               python3-all,
               python3-attr (>= 21.2) <!nocheck>,
               python3-cattr (>= 22.2) <!nocheck>,
               python3-hatchling,
               python3-itsdangerous <!nocheck>,
               python3-orjson <!nocheck>,
               python3-platformdirs (>= 2.5) <!nocheck>,
               python3-pytest <!nocheck>,
               python3-requests (>= 2.32.3+dfsg-1~) <!nocheck>,
               python3-requests-mock <!nocheck>,
               python3-responses <!nocheck>,
               python3-rich <!nocheck>,
               python3-time-machine <!nocheck>,
               python3-ujson <!nocheck>,
               python3-url-normalize (>= 3.0.1) <!nocheck>,
Standards-Version: 4.7.4.1
Testsuite: autopkgtest-pkg-pybuild
Homepage: https://github.com/requests-cache/requests-cache
Vcs-Git: https://salsa.debian.org/morph/python-requests-cache.git
Vcs-Browser: https://salsa.debian.org/morph/python-requests-cache

Package: python3-requests-cache
Architecture: all
Suggests: python3-boto3,
          python3-itsdangerous,
          python3-pymongo,
          python3-redis,
          python3-yaml,
Description: persistent HTTP cache for the requests library
 requests-cache is a persistent HTTP cache that provides an easy way to get
 better performance with the Python requests library.
 .
 Features:
 .
  * Ease of use: keep using the requests library you're already familiar with.
    Add caching with a drop-in replacement for requests.Session, or install
    globally to add transparent caching to all requests functions.
  * Performance: get sub-millisecond response times for cached responses. When
    they expire, you still save time with conditional requests.
  * Persistence: works with several storage backends including SQLite, Redis,
    MongoDB, and DynamoDB; or save responses as plain JSON files, YAML, and
    more.
  * Expiration: use Cache-Control and other standard HTTP headers, define your
    own expiration schedule, keep your cache clutter-free with backends that
    natively support TTL, or any combination of strategies.
  * Customization: works out of the box with zero config, but with a robust set
    of features for configuring and extending the library to suit your needs.
  * Compatibility: can be combined with other popular libraries based on
    requests.