views.generic.dates.MonthMixin.get_next_month()

get_next_month(date) [source] Returns a date object containing the first day of the month after the date provided. This function can also return None or raise an Http404 exception, depending on the values of allow_empty and allow_future.

db.models.PositiveSmallIntegerField

class PositiveSmallIntegerField(**options) [source] Like a PositiveIntegerField, but only allows values under a certain (database-dependent) point. Values from 0 to 32767 are safe in all databases supported by Django.

postgres.aggregates.BoolAnd

class BoolAnd(expression, **extra) [source] Returns True, if all input values are true, None if all values are null or if there are no values, otherwise False .

db.models.Field.description

description A verbose description of the field, e.g. for the django.contrib.admindocs application. The description can be of the form: description = _("String (up to %(max_length)s)") where the arguments are interpolated from the field’s __dict__. To map a Field to a database-specific type, Django exposes several methods:

Time zones

Overview When support for time zones is enabled, Django stores datetime information in UTC in the database, uses time-zone-aware datetime objects internally, and translates them to the end user’s time zone in templates and forms. This is handy if your users live in more than one time zone and you want to display datetime information according to each user’s wall clock. Even if your website is available in only one time zone, it’s still good practice to store data in UTC in your database. The ma

utils.dateparse.parse_date()

parse_date(value) [source] Parses a string and returns a datetime.date.

core.validators.RegexValidator.regex

regex The regular expression pattern to search for the provided value, or a pre-compiled regular expression. By default, raises a ValidationError with message and code if a match is not found. That standard behavior can be reversed by setting inverse_match to True, in which case the ValidationError is raised when a match is found. By default, matches any string (including an empty string).

postgres.fields.django.postgres.forms.BaseRangeField

class django.contrib.postgres.forms.BaseRangeField Base class for form range fields. base_field The form field to use. range_type The psycopg2 range type to use.

apps.apps.get_app_config()

apps.get_app_config(app_label) Returns an AppConfig for the application with the given app_label. Raises LookupError if no such application exists.

Introduction to class-based views

Class-based views provide an alternative way to implement views as Python objects instead of functions. They do not replace function-based views, but have certain differences and advantages when compared to function-based views: Organization of code related to specific HTTP methods (GET, POST, etc.) can be addressed by separate methods instead of conditional branching. Object oriented techniques such as mixins (multiple inheritance) can be used to factor code into reusable components. The rel