Django 1.6 alpha 1 released • Hacker News Board

Re: Django 1.6 alpha 1 released

#11

Post by ubernostrum » Mon, May 27, 2013, 9:23 AM UTC

Aqwis wrote: post #10

Are there usually this many backwards-incompatible changes? In the past I've usually been able to upgrade Django without having to do any significant changes in the code.

So, it's a big list. But a lot of them are either:

* Fallout from transaction changes. Whether this affects your code will vary, and when and how it can affect your code is documented, or

* Bugfixes: lots of the stuff in there consists of "we had a bug, we fixed the bug, but you should know this in case you relied on the buggy behavior".

Split those out and it's actually quite a bit shorter.

Re: Django 1.6 alpha 1 released

#12

Post by foobarram » Mon, May 27, 2013, 10:13 AM UTC

Pardon my ignorance but, `Persistent database connections`

Is this the same as pgBouncer connection pooling? It does sound like the same - but unsure. I just spent a week learning and configuring pgBouncer! :(

Re: Django 1.6 alpha 1 released

#13

Post by speg » Mon, May 27, 2013, 10:16 AM UTC

Have they moved to a faster release schedule? I feel like 1.5 just came out and we can already expect 1.6 in August (not that I'm complaining about it).

Re: Django 1.6 alpha 1 released

#14

Post by SiVal » Mon, May 27, 2013, 10:47 AM UTC

manojlds wrote: post #3

This is the most exciting and interesting thing in the release: 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.

I just read through the entire, long release document, which listed dozens of changes, large and small. Not a single mention of Python 3 that I could see (though, of course, I could have missed it.) This was supposed to have been the first version of Django in--how many years?--that the version of Python you could build production websites with was the current Python, not a legacy.

That this fact is not the headline, and apparently not even considered worthy of mention in a long list of "miscellaneous" items, suggests that those of us who aren't legacy Python 2 users (and don't ever intend to be) just aren't Django's target market. Django has been around for a relatively long time accumulating so many long-time users that I understand the desire to make supporting those who long ago entrusted their businesses to Django the #1 priority. The flip side of that, though, is that those of us without such a legacy would seem destined to be lower priority, maybe significantly lower, for at least a few more years.

If there is no Flask in the next year or so that is redesigned to focus primarily on Python 3 web dev, we'll still use Python 3 for various tasks, but for web dev it might make more sense for us to just move on to another language with a more-recently-designed framework.

Re: Django 1.6 alpha 1 released

#15

Post by crdoconnor » Mon, May 27, 2013, 11:01 AM UTC

SiVal wrote: post #14

manojlds wrote: post #3

This is the most exciting and interesting thing in the release: 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.

I just read through the entire, long release document, which listed dozens of changes, large and small. Not a single mention of Python 3 that I could see (though, of course, I could have missed it.) This was supposed to have been the first version of Django in--how many years?--that the version of Python you could build production websites with was the current Python, not a legacy. That this fact is not the headline,…

Django has supported python 3 since version 1.5 - the last major release:

https://docs.djangoproject.com/en/dev/topics/python3/

Re: Django 1.6 alpha 1 released

#16

Post by itafroma » Mon, May 27, 2013, 11:09 AM UTC

crdoconnor wrote: post #15

SiVal wrote: post #14

Earlier quoted context omitted.

I just read through the entire, long release document, which listed dozens of changes, large and small. Not a single mention of Python 3 that I could see (though, of course, I could have missed it.) This was supposed to have been the first version of Django in--how many years?--that the version of Python you could build production websites with was the current Python, not a legacy. That this fact is not the headline,…

Django has supported python 3 since version 1.5 - the last major release: https://docs.djangoproject.com/en/dev/topics/python3/

> Django has supported python 3 since version 1.5 - the last major release

Python 3 support in 1.5 was marked as "experimental"[1], with 1.6 being the release that was supposed to be marked as suitable for general use. I believe that's what GP is referring to.

[1]: https://docs.djangoproject.com/en/dev/faq/install/#can-i-use...

Re: Django 1.6 alpha 1 released

#17

Post by SiVal » Mon, May 27, 2013, 11:25 AM UTC

crdoconnor wrote: post #15

SiVal wrote: post #14

Earlier quoted context omitted.

I just read through the entire, long release document, which listed dozens of changes, large and small. Not a single mention of Python 3 that I could see (though, of course, I could have missed it.) This was supposed to have been the first version of Django in--how many years?--that the version of Python you could build production websites with was the current Python, not a legacy. That this fact is not the headline,…

Django has supported python 3 since version 1.5 - the last major release: https://docs.djangoproject.com/en/dev/topics/python3/

Yes, but 1.5 claimed only "experimental support", adding that they thought it probably would work all right but didn't want to recommend Python 3 for production yet. The unqualified "yes, we now consider it ready and can recommend Python 3 for production," was promised for Django 1.6. They probably have achieved that goal, but the fact that there is no mention of it anywhere in a document that mentions so many other things suggests that "for the first time, we can now recommend the use of Python 3 for production" isn't something they think their target market cares about as much as the several dozen other "issues" they DID mention.

Re: Django 1.6 alpha 1 released

#18

Post by Kiro » Mon, May 27, 2013, 11:47 AM UTC

elithrar wrote: post #4

manojlds wrote: post #3

This is the most exciting and interesting thing in the release: 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.

> This is the most exciting and interesting thing in the release: Absolutely. My expectation is that this alone should dramatically increase app response times for any reasonably DB-dependant application.

Typo or sarcasm?

Re: Django 1.6 alpha 1 released

#19

Post by zalew » Mon, May 27, 2013, 12:10 PM UTC

speg wrote: post #13

Have they moved to a faster release schedule? I feel like 1.5 just came out and we can already expect 1.6 in August (not that I'm complaining about it).

probably because 1.5 was the first release that didn't block master branch during the feature freeze period, so work targetting 1.6 was already progressing on master during the 1.5 bugfixing schedule.

Re: Django 1.6 alpha 1 released

#20

Post by jacobian » Mon, May 27, 2013, 12:38 PM UTC

SiVal wrote: post #14

manojlds wrote: post #3

This is the most exciting and interesting thing in the release: 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.

I just read through the entire, long release document, which listed dozens of changes, large and small. Not a single mention of Python 3 that I could see (though, of course, I could have missed it.) This was supposed to have been the first version of Django in--how many years?--that the version of Python you could build production websites with was the current Python, not a legacy. That this fact is not the headline,…

Wow, you're really making a ton of assumptions based on no evidence. I'm sorry you have such trouble assuming good faith.

Fact is, we just forgot to mention it. Django's working so well on Py3 that it kinda seems like no big deal any more, so we forgot to mention it in the release notes. I'll fix that once I get a chance.