Beaker

Latest version: v1.13.0

Safety actively analyzes 626904 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 9

0.7.4

Not secure
========================

* Fixed issue with Beaker not properly handling arguments as Pylons may pass
them in.
* Fixed unit test to catch file removal exception.
* Fixed another bug in synchronization, this one involving reentrant
conditions with file synchronization
* If a file open fails due to pickling errors, locks just opened
are released unconditionally

0.7.3

Not secure
========================

* Beaker was not properly parsing input options to session middleware. Thanks
to Yannick Gingras and Timothy S for spotting the issue.
* Changed session to only send the cookie header if its a new session and
save() was called. Also only creates the session file under these
conditions.

0.7.2

Not secure
========================

* Added deprecation warning for middleware move, relocated middleware to cache
and session modules for backwards compatibility.

0.7.1

Not secure
=======================

* adjusted synchronization logic to account for Mako/new Cache object's
multithreaded usage of Container.

0.7

Not secure
======================

* WARNING: Cleaned up Cache object based on Mako cache object, this changes
the call interface slightly for creating a Cache object directly. The
middleware cache object is unaffected from an end-user view. This change
also avoids duplicate creations of Cache objects.
* Adding database backend and unit tests.
* Added memcached test, fixed memcached namespace arg passing.
* Fixed session and cache tests, still failing syncdict test. Added doctests
for Cache and Session middleware.
* Cleanup of container/cache/container_test
* Namespaces no longer require a context, removed NamespaceContext?
* Logging in container.py uses logging module
* Cleanup of argument passing, use name **kwargs** instead of **params** for
generic kwargs
* Container classes contain a static create_namespace() method, namespaces are
accessed from the ContainerContext? via string name + container class alone
* Implemented (but not yet tested) clear() method on Cache, locates all
Namespaces used thus far and clears each one based on its keys() collection
* Fixed Cache.clear() method to actually clear the Cache namespace.
* Updated memcached backend to split servers on ';' for multiple memcached
backends.
* Merging MyghtyUtils code into Beaker.

0.6.3

Not secure
==========================

* Added api with customized Session that doesn't require a Myghty request
object, just a dict. Updated session to use the new version.
* Removing unicode keys as some dbm backends can't handle unicode keys.
* Adding core files that should've been here.
* More stringent checking for existence of a session.
* Avoid recreating the session object when it's empty.

Page 9 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.