https://github.com/jazzband/django-recurrence

Utility for working with recurring dates in Django.
https://github.com/jazzband/django-recurrence

Last synced: about 1 month ago
JSON representation

Utility for working with recurring dates in Django.

• Host: GitHub
• URL: https://github.com/jazzband/django-recurrence
• Owner: jazzband
• License: bsd-3-clause
• Created: 2012-02-20T22:41:02.000Z (about 13 years ago)
• Default Branch: master
• Last Pushed: 2024-10-03T15:02:28.000Z (6 months ago)
• Last Synced: 2025-03-05T15:53:10.794Z (about 1 month ago)
• Language: Python
• Homepage: https://django-recurrence.readthedocs.org/
• Size: 634 KB
• Stars: 503
• Watchers: 20
• Forks: 191
• Open Issues: 65
• Metadata Files:
  • Readme: README.rst
  • Changelog: CHANGES.rst
  • Contributing: CONTRIBUTING.rst
  • License: LICENSE

Awesome Lists containing this project

• awesome-django - django-recurrence - Utility for working with recurring dates in Django. (Third-Party Packages / Models)
• stars - jazzband/django-recurrence - Utility for working with recurring dates in Django. (Python)
• stars - jazzband/django-recurrence - Utility for working with recurring dates in Django. (Python)

README

        

django-recurrence

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

.. image:: https://jazzband.co/static/img/badge.svg

   :target: https://jazzband.co/

   :alt: Jazzband

.. image:: https://img.shields.io/github/stars/jazzband/django-recurrence.svg?label=Stars&style=socialcA

   :target: https://github.com/jazzband/django-recurrence

   :alt: GitHub

.. image:: https://img.shields.io/pypi/v/django-recurrence.svg

   :target: https://pypi.org/project/django-recurrence/

   :alt: PyPI release

.. image:: https://img.shields.io/pypi/pyversions/django-recurrence.svg

   :target: https://pypi.org/project/django-recurrence/

   :alt: Supported Python versions

.. image:: https://img.shields.io/pypi/djversions/django-recurrence.svg

   :target: https://pypi.org/project/django-recurrence/

   :alt: Supported Django versions

.. image:: https://img.shields.io/readthedocs/django-recurrence.svg

   :target: https://django-recurrence.readthedocs.io/

   :alt: Documentation

.. image:: https://github.com/jazzband/django-recurrence/workflows/Test/badge.svg

   :target: https://github.com/jazzband/django-recurrence/actions

   :alt: GitHub actions

.. image:: https://codecov.io/gh/jazzband/django-recurrence/branch/master/graph/badge.svg

   :target: https://codecov.io/gh/jazzband/django-recurrence

   :alt: Coverage

django-recurrence is a utility for working with recurring dates in Django.

Functionality

-------------

* Recurrence/Rule objects using a subset of rfc2445

  (wraps ``dateutil.rrule``) for specifying recurring date/times,

* ``RecurrenceField`` for storing recurring datetimes in the database, and

* JavaScript widget.

``RecurrenceField`` provides a Django model field which serializes

recurrence information for storage in the database.

For example - say you were storing information about a university course

in your app. You could use a model like this:

.. code:: python

   import recurrence.fields

   class Course(models.Model):

       title = models.CharField(max_length=200)

       start = models.TimeField()

       end = models.TimeField()

       recurrences = recurrence.fields.RecurrenceField()

You’ll notice that I’m storing my own start and end time.

The recurrence field only deals with *recurrences*

not with specific time information.

I have an event that starts at 2pm.

Its recurrences would be “every Friday”.

Documentation

-------------

For more information on installation and configuration see the documentation at:

https://django-recurrence.readthedocs.io/

Issues

------

If you have questions or have trouble using the app please file a bug report at:

https://github.com/jazzband/django-recurrence/issues

Contributions

-------------

All contributions are welcome!

It is best to separate proposed changes and PRs into small, distinct patches

by type so that they can be merged faster into upstream and released quicker.

One way to organize contributions would be to separate PRs for e.g.

* bugfixes,

* new features,

* code and design improvements,

* documentation improvements, or

* tooling and CI improvements.

Merging contributions requires passing the checks configured

with the CI. This includes running tests and linters successfully

on the currently officially supported Python and Django versions.

The test automation is run automatically with GitHub Actions, but you can

run it locally with the ``tox`` command before pushing commits.

This is a `Jazzband `_ project. By contributing you agree to abide by the `Contributor Code of Conduct `_ and follow the `guidelines `_.