Skip to content

Releases: sqlalchemy/dogpile.cache

1.1.5

19 Jan 18:24
Compare
Choose a tag to compare

1.1.5

Released: Wed Jan 19 2022

usecase

  • [usecase] [memcached] Added support for additional pymemcache HashClient parameters
    retry_attempts, retry_timeout, and
    dead_timeout.

1.1.4

02 Sep 14:45
Compare
Choose a tag to compare

1.1.4

Released: Thu Sep 2 2021

usecase

  • [usecase] [memcached] Added support for pymemcache socket keepalive and retrying client.

bug

  • [bug] [general] Fixed Python 3.10 deprecation warning involving threading. Pull request
    courtesy Karthikeyan Singaravelan.

    References: #203

1.1.3

20 May 20:08
Compare
Choose a tag to compare

1.1.3

Released: Thu May 20 2021

bug

  • [bug] [regression] [tests] Repaired the test suite to work with the 5.x series of the decorator
    module, which now appears to make use of the __signature__ attribute.

  • [bug] [regression] Fixed regression where ProxyBackend was missing several methods
    that were added as part of the 1.1 release.

    References: #202

1.1.2

26 Jan 18:52
Compare
Choose a tag to compare

1.1.2

Released: Tue Jan 26 2021

feature

  • [feature] [region] Added new region method CacheRegion.key_is_locked(). Returns True if
    the given key is subject to the dogpile lock, which would indicate that the
    generator function is running at that time. Pull request courtesy Bastien
    Gerard.

    References: #101

  • [feature] [memcached] Added support for the pymemcache backend, using the
    "dogpile.cache.pymemcache" backend identifier. Pull request courtesy
    Moisés Guimarães de Medeiros.

    References: #134

1.1.1

23 Nov 13:52
Compare
Choose a tag to compare

1.1.1

Released: Mon Nov 23 2020

bug

  • [bug] [region] Fixed regression where the serialization and deserialization functions
    could be inadvertently turned into instance methods with an unexpected
    argument signature, namely when pickle.dumps and pickle.loads are the pure
    Python version as is the case in pypy.

    References: #195

1.1.0

15 Nov 17:54
Compare
Choose a tag to compare

1.1.0

Released: Sun Nov 15 2020

feature

  • [feature] [region] Reworked the means by which values are serialized and deserialized from
    backends, and provided for custom serialization of values. Added the
    CacheRegion.serializer and
    CacheRegion.deserializer parameters which may be set to any
    serializer.

    Serialization and deserialization now take place within the
    CacheRegion so that backends may now assume string values
    in all cases. This simplifies the existing backends and also makes
    custom backends easier to write and maintain.

    Additionally, the serializer is now applied to the user-defined value
    portion of the CachedValue and not to the metadata or other
    portions of CachedValue object itself, so the serialized portion
    is effectively a "payload" within the larger CachedValue
    structure that is passed as part of the larger string format. The overall
    format is a separate JSON of the cached value metadata, followed by the
    serialized form. This allows for end-user serialization schemes that are
    hardwired to the values themselves without the need to serialize dogpile's
    internal structures as well.

    Existing custom backends should continue to work without issue; they
    now have the option to forego any separate serialization steps, and
    can also subclass a new backend BytesBackend that marks them
    as a backend that only deals with bytes coming in and out; all
    internal serialization logic from such a backend can be removed.

    Pull request courtesy Alessio Bogon.

    References: #191

misc

  • [change] Added pep-484 annotations to most of the dogpile.cache package.

1.0.2

07 Aug 17:20
Compare
Choose a tag to compare

1.0.2

Released: Fri Aug 7 2020

feature

  • [feature] [memcached] Added support for TLS connections to the bmemcached backend. Pull request
    courtesy Moisés Guimarães de Medeiros.

    References: #173

bug

  • [bug] [installation] Repaired the setup.cfg file so that the source and wheel distributions will
    not add the "tests" directory to the Python environment. Pull request
    courtesy Michał Górny.

1.0.1

21 Jul 18:56
Compare
Choose a tag to compare

1.0.1

Released: Tue Jul 21 2020

bug

  • [bug] [install] dogpile.cache 1.0.0 was released with a minimum Python version of 3.5.
    However, due to a dependency issue, the minimum version is now Python 3.6.
    The 1.0.0 release will be removed from PyPI so that Python versions prior
    to 3.6 will continue to make use of the previous dogpile.cache 0.9.2.

    References: #184

  • [bug] [installation] Removed the "universal=1" directive from setup.cfg as this would create
    py2/py3 wheels. dogpile 1.0.x is Python 3 only so a py3-only wheel is now
    created.

    References: #185

1.0.0

19 Jul 17:46
Compare
Choose a tag to compare

1.0.0

Released: Sun Jul 19 2020

feature

  • [feature] Improved plugin scanner performance by switching from pkg_resources
    to stevedore.

  • [feature] [redis] Added support for Redis Sentinel. Pull request courtesy Stéphane Brunner.
    See RedisSentinelBackend.

    References: #181

misc

  • [change: py3k] For version 1.0.0, dogpile.cache now supports Python 3.5 and above
    only.

0.9.2

04 May 20:23
Compare
Choose a tag to compare

0.9.2

Released: Mon May 4 2020

bug

  • [bug] [installation] Ensured that the "pyproject.toml" file is not included in builds, as the
    presence of this file indicates to pip that a pep-517 installation process
    should be used. As this mode of operation appears to be not well supported
    by current tools / distros, these problems are avoided within the scope of
    dogpile.cache installation by omitting the file.

    References: #178