django-recurrence is a utility for working with recurring dates in Django.
dateutil.rrule) for specifying recurring date/times,RecurrenceField for storing recurring datetimes in the database, andRecurrenceField 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:
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”.
For more information on installation and configuration see the documentation at:
https://django-recurrence.readthedocs.io/
If you have questions or have trouble using the app please file a bug report at:
https://github.com/jazzband/django-recurrence/issues
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.
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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4