News for hackers. Stuff that matters.
Re:Eighteen months of Django by jordn on Wednesday May 08, 2013 @10:34AM (#5674312)
Thanks! Basically the answer is that I wasn't aware of the possibility of those things and have tried to keep it as simple as possible.

I made a skeleton project for me as I couldn't find a decent guide for deploying django static's on s3. I fumbled my way through it and corrected and formalised it later so I could do it again. The https://github.com/rdegges/django-skel project looks really useful as it contains everything and more you might want to use for a django project (and more), though not yet knowing what magic's it's doing I wouldn't yet jump to use.

1. That is very neat. I hope to try and copy that.

2. Noted. I didn't realise the need, as python 2.7.4 is the default. Can see it causing headaches if this were to change however.

3. Why is it dangerous? I preferred to keep the version numbers so it would always just install latest versions without any extra effort.

Re:Eighteen months of Django by iends on Wednesday May 08, 2013 @07:08PM (#5677668)
The reason it's dangerous is that packages can introduce backwards incompatible changes. If you have a project that you don't work on for a few weeks/months and then need to fix a bug, you're going to have to spend additional cycles tracking down the issue and fixing either the backwards incompatible change, or adding a specific version to your requirements file anyway.

I like to try and scope the package versions at the level the maintainer promises not to introduce breakages at.