---
- branch: MAIN
  date: Sat May 16 13:56:47 UTC 2020
  files:
  - new: '1.5'
    old: '1.4'
    path: pkgsrc/devel/py-dogpile-cache/Makefile
    pathrev: pkgsrc/devel/py-dogpile-cache/Makefile@1.5
    type: modified
  - new: '1.5'
    old: '1.4'
    path: pkgsrc/devel/py-dogpile-cache/distinfo
    pathrev: pkgsrc/devel/py-dogpile-cache/distinfo@1.5
    type: modified
  id: 20200516T135647Z.74b863345032d2edce2f81248dd8415416beadaa
  log: "py-dogpile-cache: updated to 0.9.2\n\n0.9.2:\n[bug] [installation]\nEnsured
    that the 窶å¾\x98yproject.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.\n\n0.9.1:\n[bug] [tests]\nAdded decorator module as a required
    testing dependency to tox.ini so that tests work when this is not pre-installed.\n\n[bug]
    [redis]\nAdded option to the Redis backend RedisBackend.thread_local_lock, which
    when set to False will disable the use of a threading local by the redis module
    in its distributed lock service, which is known to interfere with the lock窶å\x86±
    behavior when used in an 窶å½\x97sync窶� use case, within dogpile this would
    be when using the CacheRegion.async_creation_runner feature. The default is conservatively
    being left at True, but it窶å\x86± likely this should be set to False in all
    cases, so a warning is emitted if this flag is not set to False in conjunction
    with the distributed lock. Added an optional argument to RedisBackend that specifies
    whether or not a thread-local Redis lock should be used. This is the default,
    but it breaks asynchronous runner compatibility.\n\n0.9.0:\n[feature]\nAdded logging
    facililities into CacheRegion, to indicate key events such as cache keys missing
    or regeneration of values. As these can be very high volume log messages, logging.DEBUG
    is used as the log level for the events. Pull request courtesy Stï¾\x83ｩphane
    Brunner.\n\n0.8.0:\n[bug] [setup]\nRemoved the 窶å¾\x98ython setup.py test窶�
    feature in favor of a straight run of 窶徼ox窶�. Per Pypa / pytest developers,
    窶徭etup.py窶� commands are in general headed towards deprecation in favor
    of tox. The tox.ini script has been updated such that running 窶徼ox窶� with
    no arguments will perform a single run of the test suite against the default installed
    Python interpreter.\n\n[bug] [py3k]\nReplaced the Python compatbility routines
    for getfullargspec() with a fully vendored version from Python 3.3. Originally,
    Python was emitting deprecation warnings for this function in Python 3.8 alphas.
    While this change was reverted, it was observed that Python 3 implementations
    for getfullargspec() are an order of magnitude slower as of the 3.4 series where
    it was rewritten against Signature. While Python plans to improve upon this situation,
    SQLAlchemy projects for now are using a simple replacement to avoid any future
    issues.\n\n[bug] [installation]\nPinned minimum version of Python decorator module
    at 4.0.0 (July, 2015) as previous versions don窶å\x86² provide the API that dogpile
    is using.\n\n[bug] [py3k]\nFixed the sha1_mangle_key() key mangler to coerce incoming
    Unicode objects into bytes as is required by the Py3k version of this function.\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/py-dogpile-cache'
  unixtime: '1589637407'
  user: adam