Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 1.6 released

djangoproject.com

Post reply on HN
Print view View original

1–10 of 107 posts

Re: Django 1.6 released

#6

Post by speg »

EliAndrewC wrote: post #2

The release notes can be found at https://docs.djangoproject.com/en/1.6/releases/1.6/ Personally, I'm happy that Python 3 is now officially supported, though in practice I haven't had an issues with using Django 1.5 with Python 3.

How is library support? I didn't have any issues with django 1.5 itself, but many of my favorite libraries weren't ready yet.

Re: Django 1.6 released

#7

Post by anan0s »

are there any particular performance improvements over the previous versions ?

I was thinking basically of transaction management, especially the autocommit behavior.

I browsed through the docs and saw that the default python database API requires autocommit to be turned off... but then again django overrides this behavior.

any comments on this ? (or am I completely lost ?)...

Re: Django 1.6 released

#8

Post by masklinn »

anan0s wrote: post #7

are there any particular performance improvements over the previous versions ? I was thinking basically of transaction management, especially the autocommit behavior. I browsed through the docs and saw that the default python database API requires autocommit to be turned off... but then again django overrides this behavior. any comments on this ? (or am I completely lost ?)...

> Improved transaction management¶

> Django’s transaction management was overhauled. Database-level autocommit is now turned on by default. This makes transaction handling more explicit and should improve performance. The existing APIs were deprecated, and new APIs were introduced, as described in the transaction management docs.

> Please review carefully the list of known backwards-incompatibilities to determine if you need to make changes in your code.

> Persistent database connections¶

> Django now supports reusing the same database connection for several requests. This avoids the overhead of re-establishing a connection at the beginning of each request. For backwards compatibility, this feature is disabled by default. See Persistent connections for details.

Re: Django 1.6 released

#9

Post by snoonan »

andybak wrote: post #4

django-vanilla-views in core for 1.7 please. ;-)

Thirded! This is a better implementation for a framework. CBGV as-is would be better as an add-on app.

This is a great example why framework projects could benefit from being a bit more democratic. Most people seem to be pulling their hair out, telling you something is too complicated to effectively use. The response: It's worth it once you learn. The complexity cost is worth it. Trust us. Read the docs (of course), use this 3rd party site (ok...), read the code. (so I can write a non-trivial view!?). If you are still giving that answer years later, you have to be open to the fact that that your users might be on to something.

Often when you hear someone say they're using CBGV on a large project, you can almost sense the pause for applause.

Post reply on HN