http.HttpResponse.content

HttpResponse.content A bytestring representing the content, encoded from a Unicode object if necessary.

gis.admin.GeoModelAdmin.map_height

map_height Height of the map, in pixels. Defaults to 400.

gis.gdal.GDALBand.pixel_count

pixel_count New in Django 1.9. The total number of pixels in this band. Is equal to width * height.

gis.gdal.OGRGeometry.envelope

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

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.

core.paginator.Page.has_next()

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

admin.ModelAdmin.change_view()

ModelAdmin.change_view(request, object_id, form_url='', extra_context=None) [source] Django view for the model instance editing page. See note below.

gis.geoip.GeoIP.country_name()

GeoIP.country_name(query) Returns only the country name corresponding to the query.

How to use Django with Apache and mod_wsgi

Deploying Django with Apache and mod_wsgi is a tried and tested way to get Django into production. mod_wsgi is an Apache module which can host any Python WSGI application, including Django. Django will work with any version of Apache which supports mod_wsgi. The official mod_wsgi documentation is fantastic; it’s your source for all the details about how to use mod_wsgi. You’ll probably want to start with the installation and configuration documentation. Basic configuration Once you’ve got mod_w

admin.ModelAdmin.list_filter

ModelAdmin.list_filter Set list_filter to activate filters in the right sidebar of the change list page of the admin, as illustrated in the following screenshot: list_filter should be a list or tuple of elements, where each element should be of one of the following types: a field name, where the specified field should be either a BooleanField, CharField, DateField, DateTimeField, IntegerField, ForeignKey or ManyToManyField, for example: class PersonAdmin(admin.ModelAdmin): list_filter