Django's Architecture: The Good, The Bad, and The Ugly

Django's Architecture: The Good, The Bad, and The Ugly

A talk I gave at FOSDEM 2011.

077e9a0cb34fa3eba2699240c9509717?s=128

Andrew Godwin

October 22, 2011
Tweet

Transcript

  1. 18.
  2. 24.

    from django.contrib.gis.db import models class Lakes(models.Model): name = models.CharField(max_length=100) rate

    = models.IntegerField() geom = models.MultiPolygonField() objects = models.GeoManager() >>> lake3 = Lakes.objects.get(id=3) >>> newlake.geom.contains(lake3.geom) True
  3. 25.
  4. 30.
  5. 31.
  6. 36.
  7. 43.
  8. 51.

    How do you get better? Consistency, not always writing new

    features, and people with too much free time.