Probably rarely needed but may come in handy.
These should be automatically regenerated on the fly but I’ve noticed that if you restructure your code (i.e. move things around) they can get out of whack. Best to clean them up from time to time…
Well worth a read…
Having worked in a variety of other languages, my first instinct was to create classes with static methods for things like utility libraries. But after digging around Google for a bit, it seems like this isn’t necessarily the way things are done in Python:
I’m not sure where I stand on this just yet. The logical argument is that classes should only be used for when you need to instantiate something. But sometimes it’s handy to make use of class variables. And really the only difference is a small change in syntax:
UPDATE: Looks like this shortcut method does the same thing (as long as USE_TZ = True in your settings):
The following will create a timezone-aware datetime object:
Read more here: https://docs.djangoproject.com/en/dev/topics/i18n/timezones/
Goes for sessions and just about any other type of variable:
Quick shortcut for including hidden fields in your forms:
Now you don’t have to worry about each and every hidden field.
First, check if the request.GET dict contains a parameter named q:
Now ensure the variable has a value:
Separating your views into multiple files works much the same way as models except for one difference – importing the views in __init__.py isn’t necessary unless you want to type a little less.
Without importing them in __init__, you’ll need to do this:
But if you add them, you can do the following instead: