Christ, Django is changing too fast. I recently upgraded from 1.2 to 1.3 and it's still way obsolete.
Django 1.3 was released back in March of 2011. That's more than two years ago! Were you waiting on some sort of third party package or something?
Django 1.6 beta 1 released
31–40 of 72 posts
Re: Django 1.6 beta 1 released
#32Earlier quoted context omitted.
It's not connection pooling.
Care to explain what it is?
Currently, Django closes the database connection at the end of each request/response cycle.
In 1.6, Django will optionally not do this; instead, a setting can specify the maximum amount of time to hold open and keep reusing an existing connection.
This is not connection pooling; that would imply some functionality to actively maintain and allocate connections. This is simply "your process will hold its connection open from one request/response cycle to the next".
Re: Django 1.6 beta 1 released
#33Earlier quoted context omitted.
Care to explain what it is?
Currently, Django closes the database connection at the end of each request/response cycle. In 1.6, Django will optionally not do this; instead, a setting can specify the maximum amount of time to hold open and keep reusing an existing connection. This is not connection pooling; that would imply some functionality to actively maintain and allocate connections. This is simply "your process will hold its connection ope…
Thanks for the detailed answer.
In what scenario can this be used?
Re: Django 1.6 beta 1 released
#34This can't be right: 1.5 was just released in February. It takes at least 1 year between Django releases, right? Right!? (He said, sarcastically.) Seriously, it is GREAT to see the framework continue to roll forward.
There's probably a lot of stuff that didn't make the 1.5 cut.
Re: Django 1.6 beta 1 released
#35Persistent database connections :). Glad to see the objections finally fall by the wayside.
Still no update for the homely admin app? Would love to have it use bootstrap (or similar) to offload look and feel to those focused on it. One extra thing to do in every Django app is to change the ugly yellow on cyan title bar. I know it is already possible with apps, but then it means one more thing to fix on upgrade.
Re: Django 1.6 beta 1 released
#36Integrated connection pooling makes this release a no-brainer upgrade on release day.
It is "Persistent database connections" just like it says it is.
Re: Django 1.6 beta 1 released
#37Persistent database connections :). Glad to see the objections finally fall by the wayside. Still no update for the homely admin app? Would love to have it use bootstrap (or similar) to offload look and feel to those focused on it. One extra thing to do in every Django app is to change the ugly yellow on cyan title bar. I know it is already possible with apps, but then it means one more thing to fix on upgrade.
FWIW, admin2 is under active development and moving forward. I don't know if the intention is to replace the existing admin, but as it's not backwards compatible there will be some effort to upgrade if you've completed any serious customization.
Re: Django 1.6 beta 1 released
#38Earlier quoted context omitted.
Unfortunately that's the best we have right now. However, the guy who wrote South (and is a core Django developer) ran a Kickstarter last month to raise funds to write South-like functionality directly into the Django core.
He (Andrew Godwin) also recently gave a talk on the subject, ( http://lanyrd.com/2013/djangocon-europe/schgcz/ ).
any idea when his talk will be published (youtube/pyvideo)?
Re: Django 1.6 beta 1 released
#39Earlier quoted context omitted.
Currently, Django closes the database connection at the end of each request/response cycle. In 1.6, Django will optionally not do this; instead, a setting can specify the maximum amount of time to hold open and keep reusing an existing connection. This is not connection pooling; that would imply some functionality to actively maintain and allocate connections. This is simply "your process will hold its connection ope…
Thanks for the detailed answer. In what scenario can this be used?
Think of it as an optimization: Previously, each request meant a new db connection had to be opened. Now a prior connection can be reused.
Re: Django 1.6 beta 1 released
#40This can't be right: 1.5 was just released in February. It takes at least 1 year between Django releases, right? Right!? (He said, sarcastically.) Seriously, it is GREAT to see the framework continue to roll forward.
There's probably a lot of stuff that didn't make the 1.5 cut.
1.5 was the first release after moving to git - they freeze the release branch and let the rest of development continue on master, so now releases will tend to be quicker (we all hope) hence the surprise with 'early' 1.6. now, since we have an alpha, 1.6 is bugfixed on branch, and 1.7 features can be developped on master like now during the 1.6 release schedule.