Path to this page:
Subject: CVS commit: pkgsrc/www/py-django-celery-beat
From: Adam Ciarcinski
Date: 2021-05-08 08:08:13
Message id: 20210508060813.E25B6FA95@cvs.NetBSD.org
Log Message:
py-django-celery-beat: updated to 2.2.0
2.2.0
=====
- Fixed compatibility with django-timezone-field>=4.1.0
- Fixed deprecation warnings: 'assertEquals' in tests.
- Fixed SolarSchedule event choices i18n support.
- Updated 'es' .po file metadata
- Update 'fr' .po file metadata
- New schema migrations for SolarSchedule events choices changes in models.
2.1.0
=====
- Fix string representation of CrontabSchedule, so it matches UNIX CRON \
expression format
- If no schedule is selected in PeriodicTask form, raise a non-field error \
instead of an error bounded to the `interval` field
- Fix some Spanish translations
- Log "Writing entries..." message as DEBUG instead of INFO
- Use CELERY_TIMEZONE setting as `CrontabSchedule.timezone` default instead of UTC
- Fix bug in ClockedSchedule that made the schedule stuck after a clocked task \
was executed. The `enabled` field of ClockedSchedule has been dropped
- Drop support for Python < 3.6
- Add support for Celery 5 and Django 3.1
2.0.0
=====
- Added support for Django 3.0
- Dropped support for Django < 2.2 and Python < 3.5
1.6.0
=====
- Fixed invalid long_description
- Exposed read-only field PeriodicTask.last_run_at in Django admin
- Added docker config to ease development
- Added validation schedule validation on save
- Added French translation
- Fixed case where last_run_at = None and CELERY_TIMEZONE != TIME_ZONE
1.5.0
=====
- Fixed delay returned when a task has a start_time in the future.
- PeriodicTaskAdmin: Declare some filtering, for usability
- fix _default_now is_aware bug
- Adds support for message headers for periodic tasks
- make last_run_at tz aware before passing to celery
Files: