Change history¶
2.4.0¶
| release-date: | 2011-11-04 04:00 P.M GMT |
|---|---|
| by: | Ask Solem |
Important Notes¶
This release adds South migrations, which well assist users in automatically updating their database schemas with each django-celery release.
News¶
Now depends on Celery 2.4.0 or higher.
South migrations have been added.
Migration 0001 is a snapshot from the previous stable release (2.3.3). For those who do not use South, no action is required. South users will want to read the 240-upgrade-south section below.
Contributed by Greg Taylor.
Test runner now compatible with Django 1.4.
Test runners are now classes instead of functions, so you have to change the TEST_RUNNER setting to read:
TEST_RUNNER = "djcelery.contrib.test_runner.CeleryTestSuiteRunner"
Contributed by Jonas Haag.
Upgrading for south users¶
For those that are already using django-celery 2.3.x, you’ll need to fake the newly added migration 0001, since your database already has the current djcelery_* and celery_* tables:
$ python manage.py migrate djcelery 0001 --fake
If you’re upgrading from the 2.2.x series, you’ll want to drop/reset your celery_* and djcelery_* tables and run the migration:
$ python manage.py migrate djcelery
2.3.3¶
| release-date: | 2011-08-22 12:00 AM BST |
|---|
- Precedence issue caused database backend tables to not be created (Issue #62).
2.3.1¶
| release-date: | 2011-08-11 12:00 PM BST |
|---|
Django database result backend tables were not created.
If you are having troubles because of this, be sure you do a syncdb after upgrading, that should resolve the issue.
2.3.0¶
| release-date: | 2011-08-05 12:00 PM BST |
|---|
Now depends on Celery 2.3.0
Please read the Celery 2.3.0 changelog!
2.2.4¶
celerybeat: DatabaseScheduler would not react to changes when using MySQL and the default transaction isolation level REPEATABLE-READ (Issue #41).
It is still recommended that you use isolation level READ-COMMITTED (see the Celery FAQ).
2.2.3¶
| release-date: | 2011-02-12 16:00 PM CET |
|---|
- celerybeat: DatabaseScheduler did not respect the disabled setting after restart.
- celeryevcam: Expiring objects now works on PostgreSQL.
- Now requires Celery 2.2.3
2.2.2¶
| release-date: | 2011-02-03 16:00 PM CET |
|---|
- Now requires Celery 2.2.2
- Periodic Task Admin broke if the CELERYBEAT_SCHEDULE setting was not set.
- DatabaseScheduler No longer creates duplicate interval models.
- The djcelery admin templates were not included in the distribution.
2.2.0¶
| release-date: | 2011-02-01 10:00 AM CET |
|---|
- Now depends on Celery v2.2.0
- djceleryadm: Adds task actions Kill and Terminate task
- celerycam: Django’s queryset.delete() fetches everything in memory THEN deletes, so we need to use raw SQL to expire objects.
- djcelerymon: Added Command.stdout + Command.stderr (Issue #23).
- Need to close any open database connection after any embedded celerybeat process forks.
- Added contrib/requirements/py25.txt
- Demoproject now does djcelery.setup_loader in settings.py.
2.1.1¶
| release-date: | 2010-10-14 02:00 PM CEST |
|---|
Now depends on Celery v2.1.1.
Snapshots: Fixed bug with losing events.
Snapshots: Limited the number of worker timestamp updates to once every second.
Snapshot: Handle transaction manually and commit every 100 task updates.
snapshots: Can now configure when to expire task events.
New settings:
- CELERYCAM_EXPIRE_SUCCESS (default 1 day),
- CELERYCAM_EXPIRE_ERROR (default 3 days), and
- CELERYCAM_EXPIRE_PENDING (default 5 days).
Snapshots: TaskState.args and TaskState.kwargs are now represented as TextField instead of CharField.
If you need to represent arguments larger than 200 chars you have to migrate the table.
transaction.commit_manually doesn’t accept arguments on older Django version.
Should now work with Django versions previous to v1.2.
The tests doesn’t need unittest2 anymore if running on Python 2.7.
2.1.0¶
| release-date: | 2010-10-08 12:00 PM CEST |
|---|
Important Notes¶
This release depends on Celery version 2.1.0. Be sure to read the Celery changelog before you upgrade: http://ask.github.com/celery/changelog.html#version-2-1-0
News¶
The periodic task schedule can now be stored in the database and edited via the Django Admin interface.
To use the new database schedule you need to start celerybeat with the following argument:
$ python manage.py celerybeat -S djcelery.schedulers.DatabaseScheduler
Note that you need to add your old periodic tasks to the database manually (using the Django admin interface for example).
New Celery monitor for the Django Admin interface.
To start monitoring your workers you have to start your workers in event mode:
$ python manage.py celeryd -E
(you can do this without restarting the server too:
>>> from celery.task.control import broadcast >>> broadcast("enable_events")
You need to do a syncdb to create the new tables:
python manage.py syncdb
Then you need to start the snapshot camera:
$ python manage.py celerycam -f 2.0
This will take a snapshot of the events every 2 seconds and store it in the database.
2.0.2¶
Important notes¶
Due to some applications loading the Django models lazily, it is recommended that you add the following lines to your settings.py:
import djcelery djcelery.setup_loader() This will ensure the Django celery loader is set even though the model modules haven't been imported yet.
