On 10/18/11 08:46, Dan Gentry wrote:
With all due respect to Mr. Gonsalves, I do not care to work with the Django trunk unless I'm just playing around with something. My goal is always to produce a production quality application. Even the more stable than average Django trunk cannot provide the consistency needed to deliver an app to a customer. Plus, I don't need the extra work of basing my code on a moving target. When trunk becomes v1.4, I will convert my applications and upgrade.
I often have both in parallel. Using git (or mercurial...I use both/either) makes it fast & easy to switch between trunk and the latest stable version to see what breaks.
For my personal/development projects I tend to develop against trunk but test against 1.3; and I flip that for my production/professional projects, developing against 1.3 but testing occasionally against a checkout of trunk in an effort to prepare for the next release.
One of the other areas I hear a lot about but haven't tinkered with is learning to work well with virtualenv and pip. I tend to run stock Debian(Stable) and just use whatever comes with the setup, but a number of folks sandbox their dev efforts into a virtualenv playground.
-tim -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
