Django-apscheduler

Latest version: v0.6.2

Safety actively analyzes 613568 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

0.6.2

**Fixes**

- Make and commit missing migrations (Resolves [165](https://github.com/jcass77/django-apscheduler/issues/165)).

0.6.1

**Fixes**

- Also handle `db.InterfaceError` when retrying database-related operations (thanks zmmfsj-z).
- Add `unique_job_executions` constraint to ensure that only one `DjangoJobExecution` can be created for
each `DjangoJob` for a specific run time (Mitigates [156](https://github.com/jcass77/django-apscheduler/issues/156)).
- Update CI configuration to test on Django 3.2 and 4.0, and Python 3.10 (
Resolves [163](https://github.com/jcass77/django-apscheduler/issues/163)).
- Drop official support for Django<3.2 and Python<3.8. This is slightly ahead of the official dates published in
https://www.djangoproject.com/download/ and https://devguide.python.org/#status-of-python-branches, but makes the test
workflows simpler and easier to maintain. If you are using older releases they **might** still work...

0.6.0

**Fixes**

- Fix screenshot links in README to work on PyPI.
- Remove reference to deprecated `django.utils.translation.ugettext_lazy`.

**Enhancements**

- The Django admin page will now show a list of all the manually triggered jobs that could not be completed
before `settings.APSCHEDULER_RUN_NOW_TIMEOUT` seconds elapsed.
- Make more of the string output on the admin page Django-translatable.
- Introduce a `retry_on_db_operational_error` utility decorator for retrying database-related operations when
a `django.db.OperationalError` is encountered (Partial resolution
of [145](https://github.com/jcass77/django-apscheduler/issues/145)).
- Introduce a `close_old_connections` utility decorator to enforce Django's `CONN_MAX_AGE` setting. (Partial resolution
of [145](https://github.com/jcass77/django-apscheduler/issues/145) - thanks bluetech). **This decorator should be
applied to all of your jobs that require access to the database.**

0.5.2

**Enhancements**

- Include Python 3.9 in continuous integration runs.
- Switch from Travis-CI to GitHub Actions.

0.5.1

**Fixes**

- Pin dependency to APScheduler < 4.0, which appears to be introducing
some [backwards incompatible changes](https://github.com/agronholm/apscheduler/issues/465).
- Update readme to clarify the need for ensuring that a single scheduler is run in your Django application until
APScheduler 4.0 arrives and django-apscheduler is migrated to make use of that version.
- Update authors section in `setup.py`.
- Don't try to log job executions for jobs that are no longer available in the job store. This was partially fixed
previously as part of [116](https://github.com/jcass77/django-apscheduler/issues/116), which only catered for
'execution' type of events. This fix resolves the issue for the remaining 'submitted' and 'error' events as well
(Fixes [121](https://github.com/jcass77/django-apscheduler/issues/121)).

0.5.0

**Enhancements**

- Add ability to trigger a scheduled job manually from the `DjangoJobAdmin` page (
Resolves [102](https://github.com/jcass77/django-apscheduler/issues/102)).
- The `register_job` decorator has been deprecated. Please use APScheduler's `add_job()` method or `scheduled_job`
decorator instead (Resolves [119](https://github.com/jcass77/django-apscheduler/pull/119)).

**Fixes**

- Don't try to log job executions for jobs that are no longer available in the job store (
Fixes [116](https://github.com/jcass77/django-apscheduler/issues/116)).

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.