./www/py-django-celery-beat, Database-backed Periodic Tasks

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 2.2.1, Package name: py38-django-celery-beat-2.2.1, Maintainer: pkgsrc-users

This extension enables you to store the periodic task schedule in the database.

The periodic tasks can be managed from the Django Admin interface, where you
can create, edit and delete periodic tasks and how often they should run.


Required to run:
[devel/py-setuptools] [lang/python27] [net/py-celery] [sysutils/py-crontab]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: b6ed357bf422c78cbc5179aa7fd2044f191eaf32
RMD160: 374acc363c8ee2fcf25b7f4718939df8b67f085a
Filesize: 96.702 KB

Version history: (Expand)


CVS history: (Expand)


   2021-07-22 15:36:42 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-django-celery-beat: updated to 2.2.1

2.2.1
- Enable Django 3.2 CI and add default_auto_field
- Fix locale in dir tree
- Do not blindly delete duplicate schedules
- used python:3.8-slim for lighter builds
- Do not blindly delete duplicate schedules
   2021-05-08 08:08:13 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
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
   2019-01-07 13:59:36 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-django-celery-beat: updated to 1.4.0

1.4.0:
- Fix migrations dependencies.
- Added the DJANGO_CELERY_BEAT_TZ_AWARE setting.

1.3.0:
- Fix transaction handling while syncing the schedule.
- Fix schedule type validation logic.
- Scheduler no longer forgets the tasks after first schedule change.
- Fix race condition for schedule_changed() resulting in erroneously closed \ 
connections.
- Add support for task priorities when using RabbitMQ or Redis as broker.
- Disabled tasks are now correctly deleted from the schedule.
- Added name as search filter.

1.2.0:
- Allow timezone-aware Cron schedules.
- Retry later in case of InterfaceError in sync.
- Show Periodic Task Description in panel admin.
- Fix CrontabSchedule example.
- Support Periodic Tasks with a start date and one-off tasks.
- Fixes a problem with beat not reconnecting to MySQL (server restart, network \ 
problem, etc.) when checking if schedule has changed.
- Add toggle admin action which allows to activate disabled tasks or deactivate \ 
enabled tasks.
- Add fields validation for CrontabSchedule.
- Drop support for Django<1.11.
- Fix task heap invalidation bug which prevented scheduled tasks from running \ 
when syncing tasks from the database.
- Raise a ValidationError when more than one type (solar, crontab or interval) \ 
of schedule is provided.
   2018-02-22 11:30:38 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-django-celery-beat: updated to 1.1.1

1.1.1
- Fix interval schedules by providing nowfun.
- Removing code that forced last_run_at to be timezone naive for no reason, made \ 
timezone aware. Fixes crontab schedules
- Entry.last_run_at is no-longer timezone naive.
- Use a localized PyTZ timezone object for now() otherwise conversions fail \ 
scheduling breaks resulting in constant running of tasks or possibly not running \ 
ever.
- Fix endless migrations creation for solar schedules events.
- Prevent MySQL has gone away errors.
- Added support for Django 2.0.
- Adjust CrontabSchedule's minutes, hour & day_of_month fields max length
   2018-01-11 15:35:40 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
py-django-celery-beat: added version 1.1.0

This extension enables you to store the periodic task schedule in the database.

The periodic tasks can be managed from the Django Admin interface, where you
can create, edit and delete periodic tasks and how often they should run.