auth.views.login()

login(request, template_name=`registration/login.html`, redirect_field_name='next', authentication_form=AuthenticationForm, current_app=None, extra_context=None, redirect_authenticated_user=False) URL name: login See the URL documentation for details on using named URL patterns. Optional arguments: template_name: The name of a template to display for the view used to log the user in. Defaults to registration/login.html. redirect_field_name: The name of a GET field containing the URL to red

auth.models.CustomUserManager.create_superuser()

create_superuser(*username_field*, password, **other_fields) The prototype of create_superuser() should accept the username field, plus all required fields as arguments. For example, if your user model uses email as the username field, and has date_of_birth as a required field, then create_superuser should be defined as: def create_superuser(self, email, date_of_birth, password): # create superuser here ... Unlike create_user(), create_superuser() must require the caller to provide

admin.InlineModelAdmin.classes

InlineModelAdmin.classes New in Django 1.10. A list or tuple containing extra CSS classes to apply to the fieldset that is rendered for the inlines. Defaults to None. As with classes configured in fieldsets, inlines with a collapse class will be initially collapsed and their header will have a small “show” link.

db.models.Field.editable

Field.editable If False, the field will not be displayed in the admin or any other ModelForm. They are also skipped during model validation. Default is True.

admin.ModelAdmin.has_add_permission()

ModelAdmin.has_add_permission(request) Should return True if adding an object is permitted, False otherwise.

core.paginator.Page.has_next()

Page.has_next() [source] Returns True if there’s a next page.

db.models.ForeignKey.db_constraint

ForeignKey.db_constraint Controls whether or not a constraint should be created in the database for this foreign key. The default is True, and that’s almost certainly what you want; setting this to False can be very bad for data integrity. That said, here are some scenarios where you might want to do this: You have legacy data that is not valid. You’re sharding your database. If this is set to False, accessing a related object that doesn’t exist will raise its DoesNotExist exception.

gis.gdal.OGRGeometry.envelope

envelope Returns the envelope of this geometry, as an Envelope object.

gis.gdal.GDALRaster.srid

srid New in Django 1.10. The Spatial Reference System Identifier (SRID) of the raster. This property is a shortcut to getting or setting the SRID through the srs attribute. >>> rst = GDALRaster({'width': 10, 'height': 20, 'srid': 4326}) >>> rst.srid 4326 >>> rst.srid = 3086 >>> rst.srid 3086 >>> rst.srs.srid # This is equivalent 3086

db.models.query.QuerySet.get_or_create()

get_or_create(defaults=None, **kwargs) A convenience method for looking up an object with the given kwargs (may be empty if your model has defaults for all fields), creating one if necessary. Returns a tuple of (object, created), where object is the retrieved or created object and created is a boolean specifying whether a new object was created. This is meant as a shortcut to boilerplatish code. For example: try: obj = Person.objects.get(first_name='John', last_name='Lennon') except Pers