Django-scheduler

Latest version: v0.10.1

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

Scan your dependencies

Page 2 of 4

0.9.1

==================

- Removed support for end-of-life Django 2.0.
- ``Calendar.slug`` is now unique.
- ``Event.rule`` and ``Event.creator`` foreign keys are now
``on_delete=models.SET_NULL``.

0.9.0

==================

- Added support for Django 2.1, 2.2, and 3.0 and Python 3.7.
- Dropped support for Python 2.7 and 3.4.
- Added support for FullCalendar's use of the ``%Y-%m-%dT%H:%M:%S`` datetime
format.
- Added the ``__hash__`` method to the ``Occurrence`` model to fix a crash when
deleting objects with Django ≥ 2.2.

0.8.8

==================

- Fixed dependencies to keep Django 1.11 support.
- ``Event.calendar`` is now ``null=True``. Existing ``Event`` objects without a
calendar will be assigned to a calendar named "default".

0.8.7

==================

- Added support for Django 2.0.
- Removed support for Django < 1.11.
- Removed support for end of life Python 3.3.
- Removed ``SCHEDULER_BASE_CLASSES`` setting.
- ``Calendar.slug`` is now ``unique=True``.
- To improve query performance, generic foreign keys are now ``db_index=True``.

0.8.6

==================

- Fixed admin to use ``SCHEDULER_ADMIN_FIELDS`` for ``Calendar``.
- Fixed compatibility with dateutil 2.6.1.
- Added missing migration for the ``Calendar`` ``verbose_name`` option.

0.8.5

==================

- Model fields of type ``CharField`` or ``TextField`` are now ``null=False``.
Use an empty string, ``''``, to represent no data.
- ``feeds/atom.py`` has been removed. Use Django's syndication feed framework
instead.
- Added setting ``SCHEDULER_ADMIN_FIELDS`` to add additional fields to be added
to admin forms.
- Changed ``Callendar`` ``verbose_name`` to "calendars".

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.