When I use django for development, I usually need multiple versions of settings.py file for my project.One for development and one for production. My current approach to solve multiple settings file problem is using tree files. In my project directory I have following

---

Django does not provide any standard way of organizing thumbnails. Even though community has some applications to work with thumbnails, they are usually over kill if You only want to create a thumbnail for an ImageField. So here is my solution to handle thumbnails...

---

Recently, I decided to build my development environments on a python virtualenv, so project dependencies will not clobber global python path. Here is how I start a default django project from scratch...

---

This is the follow up for basic emacs setup post. In this post I will explain how to update your emacs setup for web development. I will cover

• Add nxhtml (Enhanced html,css mode)
• Add js2 (Enhanced javascript mode)
• Add jslint (jslint checker for emacs)

---

This is the follow up for basic emacs setup post. In this post I will explain how to update your emacs setup for python development. I will cover

• pymacs (Python binding for emacs. This is a ropemacs dependency)
• rope (Python refactoring library)
• ropemacs (Rope bindings for emacs)
• rope-mode (Minor mode for ropemacs)
• pyflakes (passive checker of Python programs)
• flymake (an on-the-fly syntax checker for GNU Emacs)
• flymake-mode (Minor mode for flymake)
• pyflakes error format script
• autocomplete rope integration

---

This is the second part of the two-part series. First part can be found here. Here are some more tips that every django developer should know in order to write faster apps....

---

This blog post will be split into two part. After I finish part two, I will add a link at the bottom of this one. For both parts I will use a sample project with sqlite3 database. models.py file for sample application is here...

---