NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #967 most downloaded on PyPI
a little task queue
Last release 14 days ago
04 Sep 2026
Release timing varies
gaps range from 8 days to 7 months
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
15 years old
87 releases · first in 2012
Adds flag to preserve result-store value in certain circumstances. Contains yet more hacking at the consumer configuration options, specifically hard-
Adds flag to preserve result-store value in certain circumstances. Contains yet more hacking at the consumer configuration options, specifically hard-coded defaults are removed from the option definitions.
The run_huey management command was simplified as we are dropping support for
older (officially unsupported) versions of Django.
Added a sqlitedb contrib module that uses a local SQLite database instead of
Redis for Queue persistence, task scheduling and result-storage.
Adds flag to preserve result-store value in certain circumstances. Contains yet more hacking at the consumer configuration options, specifically hard-coded defaults are removed from the option definitions.
The run_huey management command was simplified as we are dropping support for
older (officially unsupported) versions of Django.
Added a sqlitedb contrib module that uses a local SQLite database instead of
Redis for Queue persistence, task scheduling and result-storage.
Contains an attempt at fixing the django management command handling of the
default option.
Contains small bugfix for an earlier bugfix meant to prevent time.sleep() from being called with a negative time interval.
One column per quarter.
Contains an attempt at fixing the django management command handling of the default option.
Contains an attempt at fixing the django management command handling of the
default option.
Contains small bugfix for an earlier bugfix meant to prevent time.sleep() from being called with a negative time interval.
Contains small bugfix for an earlier bugfix meant to prevent time.sleep() from being called with a negative time interval.
Nothing published for this version
Removed the metadata APIs added in 1.1.0, as they seemed poorly-designed and altogether a decent idea terribly implemented. Perhaps something I'll rev
Removed the metadata APIs added in 1.1.0, as they seemed poorly-designed and altogether a decent idea terribly implemented. Perhaps something I'll revisit, but which should be easy to implement as a third-party library using the events APIs.
AsyncData is renamed to TaskResultWrapper.Huey.result() is a new method that provides the result of a task, given a
task ID.Removed the metadata APIs added in 1.1.0, as they seemed poorly-designed and altogether a decent idea terribly implemented. Perhaps something I'll revisit, but which should be easy to implement as a third-party library using the events APIs.
AsyncData is renamed to TaskResultWrapper.Huey.result() is a new method that provides the result of a task, given a
task ID.I've added a new API for fetching a task's result given on the task's ID. You
can now call huey.result(task_id) and retrieve the result if the task has
finished executing. Additionally, the Huey.result
method accepts the same parameters as AsyncData.get,
allowing you to block for results, specify a timeout, etc.
There is also a new parameter on the above methods, preserve=False. By
default, the result store will delete a task result once it has been read. Specifying
preserve=True ensures the data is not removed.
This is a small release with a couple minor bugfixes.
I've added a new API for fetching a task's result given on the task's ID. You can now call huey.result(task_id) and retrieve the result if the task ha
I've added a new API for fetching a task's result given on the task's ID. You
can now call huey.result(task_id) and retrieve the result if the task has
finished executing. Additionally, the Huey.result
method accepts the same parameters as AsyncData.get,
allowing you to block for results, specify a timeout, etc.
There is also a new parameter on the above methods, preserve=False. By
default, the result store will delete a task result once it has been read. Specifying
preserve=True ensures the data is not removed.
This is a small release with a couple minor bugfixes.
This is a small release with a couple minor bugfixes.
Big changes to simplify the way Huey is instantiated. No changes should be necessary if already using RedisHuey.
Huey is instantiated. No changes should
be necessary if already using RedisHuey.Huey is instantiated. No changes should
be necessary if already using RedisHuey.What follows is a description of the changes between 0.4.9 and 1.0.0. There are some backwards-incompatible changes to be aware of as well as new options for the consumer. Most APIs are the same, however.
Backwards incompatible changes:
huey.djhuey moved to huey.contrib.djhuey. You will need to update
any import statements as well as your Django INSTALLED_APPS setting to
reflect the new module path.huey.backends.redis_backend to huey.storage.-t and --threads option from the consumer. You should now
use -w or --workers.-p and --periodic no-op options from the consumer. These
are enabled by default so the option had no meaning.scheduler-interval option is configured using -s when previously
it was -S. Furthermore, this must be a value between 1 and 60.peewee_helpers module.New features:
pending(), scheduled() and all_results() methods to the Huey
class to allow introspection of the Queue's state at the current moment in
time.Backwards incompatible changes:
What follows is a description of the changes between 0.4.9 and 1.0.0. There are some backwards-incompatible changes to be aware of as well as new options for the consumer. Most APIs are the same, however.
Backwards incompatible changes:
huey.djhuey moved to huey.contrib.djhuey. You will need to update
any import statements as well as your Django INSTALLED_APPS setting to
reflect the new module path.huey.backends.redis_backend to huey.storage.-t and --threads option from the consumer. You should now
use -w or --workers.-p and --periodic no-op options from the consumer. These
are enabled by default so the option had no meaning.scheduler-interval option is configured using -s when previously
it was -S. Furthermore, this must be a value between 1 and 60.peewee_helpers module.New features:
pending(), scheduled() and all_results() methods to the Huey
class to allow introspection of the Queue's state at the current moment in
time.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →