Django community: Django links RSS
This page, updated regularly, aggregates Django links from the Django community.
-
Overview — Velruse v0.1 documentation
-
Using Signals to Create User Profiles in Django 1.3 | Floruit
-
Rails/Django Comparison
-
Django deployment workshop
-
Django Deployment Workshop - PyCon US Videos - 2009, 2010 ...
-
Python Package Index : django-primate 0.1
-
Use Django and jQuery to create a spreadsheet application
-
Using Signals to Create User Profiles in Django 1.3 | Floruit
-
Whiskey Media
-
How to construct a web developer in twelve months
Decent list of resources and tips for the budding programmer/hacker/entrepreneur. My personal advice: Focus on the BUILD & PLAY portions. -
Using Signals to Create User Profiles in Django 1.3 | Floruit
-
washingtontimes/django-categories - GitHub
-
Django Packages : django reusable apps, sites and tools directory
packages pr fer de tots en django -
Django patterns, part 2: efficient reverse lookups
One of the main sources of unnecessary database queries in Django applications is reverse relations. By default, Django doesn't do anything to follow relations across models. This means that unless you're careful, any relationship can lead to extra hits on the database. For instance, assuming MyModel has a ForeignKey to MyRelatedModel, this: myobj = MyModel.objects.get(pk=1) print myobj.myrelatedmodel.name hits the database two separate times - once to get the MyModel object, and once to get the related MyRelatedModel object. Luckily, it's easy to get Django to optimise this into a single call: myobj = MyModel.objects.select_related.get(pk=1) This way Django does a JOIN in the database call, and caches the related object in a hidden attribute of myobj. Printing myobj.__dict__ will show this: {'_myrelatedmodel_cache': [MyRelatedModel: obj], 'name': 'My name'} Now, whenever you call myobj.myrelatedmodel, Django automatically uses the version in _myrelatedmodel_cache rather than going back to the database to get it. Note that this is exactly the same as what happens once the the related object was accessed in the first snippet above - Django caches it in the same way for future use. All select_related() does is pre-cache it before the first access. None of this is new - it's quite well … -
Django tips: the difference between 'blank' and 'null'
-
smugmug-for-django - Quick, lightweight solution for adding a SmugMug to a Django site - Google Project Hosting
-
jaylett/django_exceptional_middleware - GitHub
"Middleware app that makes it easy to generate the correct HTTP status codes, with customisable templates, for more rare situations than Django supports, and making it easy to style them all the same way." -
jezdez/django-relationships - GitHub
-
Django compressor — Django compressor v0.6b4 documentation
-
jezdez/django_compressor - GitHub
-
Hyde - A Python Static Website Generator
-
Django | Unicode data | Django documentation
-
Django | Model field reference | Django documentation
-
Use Django and jQuery to create a spreadsheet application
-
lurkingideas of Jiri Barton