Skip to content

Commit

Permalink
2.1.0
Browse files Browse the repository at this point in the history
  • Loading branch information
coleifer committed Jun 6, 2019
1 parent 1677be3 commit ec98ddd
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 3 deletions.
17 changes: 15 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,10 @@ Changelog

## master

[View commits](https://github.com/coleifer/huey/compare/2.1.0...HEAD)

## 2.1.0

* Added new contrib module `sql_huey`, which uses `peewee <https://github.com/coleifer/peewee>`_
to provide storage layer using any of the supported databases (sqlite, mysql
or postgresql).
Expand All @@ -11,8 +15,17 @@ Changelog
this storage implementation must keep all result keys at the top-level Redis
keyspace. There are some small changes to the storage APIs as well, but will
only possibly affect maintainers of alternative storage layers.

[View commits](https://github.com/coleifer/huey/compare/2.0.1...HEAD)
* Also added a `PriorityRedisExpireHuey` which combines the priority-queue
support from `PriorityRedisHuey` with the result-store expiration mechanism
of `RedisExpireHuey`.
* Fix gzip compatibility issue when using Python 2.x.
* Add option to `Huey` to use `zlib` as the compression method instead of gzip.
* Added `FileStorageMethods` storage mixin, which uses the filesystem for task
result-store APIs (put, peek, pop).
* The storage-specific `Huey` implementations (e.g. `RedisHuey`) are no longer
subclasses, but instead are partial applications of the `Huey` constructor.

[View commits](https://github.com/coleifer/huey/compare/2.0.1...2.1.0)

### 2.0.1

Expand Down
2 changes: 1 addition & 1 deletion huey/__init__.py
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
__author__ = 'Charles Leifer'
__license__ = 'MIT'
__version__ = '2.0.1'
__version__ = '2.1.0'

from huey.api import BlackHoleHuey
from huey.api import Huey
Expand Down

0 comments on commit ec98ddd

Please sign in to comment.