ModelAdmin.response_delete(request, obj_display, obj_id) [source] Determines the HttpResponse for the delete_view() stage. response_delete is called after the object has been deleted. You can override it to change the default behavior after the object has been deleted. obj_display is a string with the name of the deleted object. obj_id is the serialized identifier used to retrieve the object to be deleted.

ModelAdmin.add_form_template Path to a custom template, used by add_view().

is_naive(value) [source] Returns True if value is naive, False if it is aware. This function assumes that value is a datetime.

class HttpResponsePermanentRedirect [source] Like HttpResponseRedirect, but it returns a permanent redirect (HTTP status code 301) instead of a “found” redirect (status code 302).

class RenameModel(old_name, new_name) [source] Renames the model from an old name to a new one. You may have to manually add this if you change the model’s name and quite a few of its fields at once; to the autodetector, this will look like you deleted a model with the old name and added a new one with a different name, and the migration it creates will lose any data in the old table.

GEOSGeometry.interpolate_normalized(distance) Given a distance (float), returns the point (or closest point) within the geometry (LineString or MultiLineString) at that distance. The normalized version takes the distance as a float between 0 (origin) and 1 (endpoint). Reverse of GEOSGeometry.project().

num_feat Returns the number of features in the layer. Same as len(layer): >>> layer.num_feat 3

class AlterModelOptions(name, options) [source] Stores changes to miscellaneous model options (settings on a model’s Meta) like permissions and verbose_name. Does not affect the database, but persists these changes for RunPython instances to use. options should be a dictionary mapping option names to values.

date_field The name of the DateField or DateTimeField in the QuerySet’s model that the date-based archive should use to determine the list of objects to display on the page. When time zone support is enabled and date_field is a DateTimeField, dates are assumed to be in the current time zone. Otherwise, the queryset could include objects from the previous or the next day in the end user’s time zone. Warning In this situation, if you have implemented per-user time zone selection, the same URL

put(*args, **kwargs) The PUT action is also handled and just passes all parameters through to post().