django-slots allows arbitrary Django models to be scheduled against one another, with time as a feature of that relationship. The relationship can either start at a particular time, until the next change occurs: this is called a transition; or the relationship can occur explicitly between a start and end time: this is called a slot. Think of them both as time-based foreign keys.

Some documentation

None of the documentation mentions transitions, which is a pain in the arse because they are actually more fully featured (eg, you can use them in the admin). It's possible the code is simple and well documented/commented enough that its usage can be figured out without documentation.

This documentation, therefore, is related to slots. Note that the patterns used when writing transitions has lead me to think that the slots approach is daft and can be simplified. In particular the GenericIntermediaries stuff is properly overkill, as well as being the number one reason why an admin interface never sprang into life. Nonetheless this stuff might be useful anyway:

• Introducing django-slots is, as the name suggests, an introduction to what this project is about.
• There is a very terse guide to getting django-slots up and running.
• Slots and schedules are also explained in a little more depth.
• Generic intermediaries, the mechanism which underlies the implementation of slots, is documented too.

django-slots was started by Darren Foreman. The code is released under a BSD license, and is © Darren Foreman 2008.