django-vanilla-views in core for 1.7 please. ;-)
Was unaware of this project, thanks for bringing it up. Just about to begin a major project of my own, and it will definitely come in handy.
Django 1.6 released
91–100 of 107 posts
Re: Django 1.6 released
#92Now that we have 1.6, what should we expect for 1.7?
Re: Django 1.6 released
#93The dedication to Malcolm Tredinnick was a very nice thing for the Django team to do. I didn't know of Malcolm or his passing before reading the release notes, but he seemed like a wonderful person who will be missed by many. Very sad that somebody like that is no longer with us. Reading his tweets I get the sense he was a really cool guy. Really nice piece about Malcolm from his former boss: https://plus.google.com/…
Isn't two scoops also dedicated to Malcolm Tredinnick?
Re: Django 1.6 released
#94Dumb question: What does it mean that autocommit is now turned on? I no longer have to call mymodel.save()?
https://docs.djangoproject.com/en/dev/releases/1.6/#improved...
Re: Django 1.6 released
#95For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…
Working with frontend designers/developers in a few different languages (PHP/Python), the easiest way for our office was to just use a central development server in the office then use NFS.
Sourcetree is a little slow for them (they use Macs), but they seem to get the idea.
Re: Django 1.6 released
#96One of the reasons I like Django so much is because of the community. This might seem rather meta but the comments in this thread are generally positive. Most Django users I know are well aware of its limitations and don't try to sugarcoat it if Django is not the right tool for the job. But overall I've found the community (and that of Python) pretty receptive.
What jobs is Django the right tool for?
Re: Django 1.6 released
#97If you were starting a new project today, would you use development version 1.7 in order to get Django Migrations instead of using South?
1.7 It is not hard to keep up with changes. And it is easier to do them incrementally than have big jump which you never find time to do and end up lagging versions and huge technical debt.
Once your project is deployed then think about sticking with specific version. Development should be on the bleeding edge!
Re: Django 1.6 released
#98For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…
Tell them to learn or get a new job. This is basic literacy in our industry.
Re: Django 1.6 released
#991.7 release will be very interesting. Instead of South there will be migrations support. At DjangoCon EU Andrew Godwin told about his vision of it. i.e. if you have 200 migrations you'll be able to merge them into 1.
Form fields will get extended support like input[type="email"]
Django comments are now deprecated.
Congratulations to everyone using Django!
Re: Django 1.6 released
#100Earlier quoted context omitted.
Boto (using SES for email) is main one. And supervisord if you want to keep your deployment Python 3 only.
Circus is Python 3 compatible if people are looking for an alternative to supervisor. There's always the option of just using Upstart or systemd as well.
Circus looks huge and doesn't appeal for one or two apps. I do however wish to experiment with circus at some point. Do you have any comparison to make, assuming you have used both? Or anyone out there? Thanks