News for hackers. Stuff that matters.
Re:Ask HN: State of Django vs. Rails? by icn2 on Tuesday February 19, 2013 @07:20PM (#5248128)
I have more experiences on django. Recently I looked into ruby on rails and I don't want to look back. * bundle install. In ruby everything is a gem when you deploy to a new machine all you need to do is "bundle install". In django I really don't see a comparable facility. I recall I forgot something until I got an "import module error" * scaffold. ruby on rails scaffold just makes development usper fast. * dev/test/production config. Well it is just very convenient. * db migration. migration make db update/change much easier. Changing db/data schema is so painful in django.
Re:Ask HN: State of Django vs. Rails? by beatpanda on Tuesday February 19, 2013 @07:30PM (#5248169)
There's a comparable facility that's part of Django best practices, but it's not bundled with Django. It's a pip requirements.txt file.

Substitute 'bundle install' for 'pip install -r requirements.txt' and it's basically the same thing.

Re:Ask HN: State of Django vs. Rails? by aGHz on Tuesday February 19, 2013 @07:35PM (#5248191)
It bears mentioning that this is usually done in conjunction with virtualenv. The common practice is to include a requirements file in your repository, and have every repo clone live in its own virtualenv. This is something I very much love in the Python world: encapsulation of deployments is separate from package management.