21–30 of 107 posts
Is it only me or it's not easy to discover what's new / changed / release notes from this page? Is there a secret link I'm missing?
The announcement and release notes both have the information you want:
https://www.djangoproject.com/weblog/2013/nov/06/django-16-r...
Earlier quoted context omitted.
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.
Django Packages lists 160 apps that work with Python 3. See https://www.djangopackages.com/python3/ From personal experience, most of the critical ones are compatible.
Earlier quoted context omitted.
Django Packages lists 160 apps that work with Python 3. See https://www.djangopackages.com/python3/ From personal experience, most of the critical ones are compatible.
Boto (using SES for email) is main one. And supervisord if you want to keep your deployment Python 3 only.
Still in progress, but there you go.
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…
Looks like somebody jumped the gun when they saw the commits and uploads happening; the official release announcement went up only a few minutes ago, and is here: https://www.djangoproject.com/weblog/2013/nov/06/django-16-r... The release notes are here: https://docs.djangoproject.com/en/1.6/releases/1.6/ Also: if you downloaded the package in the period between the parent link going up, and now, you might want to gr…
Was the release uploaded to pypi or a download page? If so, that's released IMHO. eg, debian, various news outlets, and others auto scan download pages for new releases.
Looks like somebody jumped the gun when they saw the commits and uploads happening; the official release announcement went up only a few minutes ago, and is here: https://www.djangoproject.com/weblog/2013/nov/06/django-16-r... The release notes are here: https://docs.djangoproject.com/en/1.6/releases/1.6/ Also: if you downloaded the package in the period between the parent link going up, and now, you might want to gr…
Seems like a new release should be done? Isn't that what RC and pre releases are for? Was the release uploaded to pypi or a download page? If so, that's released IMHO. eg, debian, various news outlets, and others auto scan download pages for new releases.
And if we catch a minor packaging error at this point, it's easy enough to fix on the spot without having to do an entire new release.
Except in this case somebody got really eager, saw the release process starting, and posted a link to our downloads page (and I'm not entirely certain if it would have been possible to get the incorrect package from it), rather than waiting for and linking to the release announcement once we'd vetted and made everything public.
Earlier quoted context omitted.
Seems like a new release should be done? Isn't that what RC and pre releases are for? Was the release uploaded to pypi or a download page? If so, that's released IMHO. eg, debian, various news outlets, and others auto scan download pages for new releases.
Well, what we do is generate everything, then share it privately and quickly amongst the core team for final review before flipping switches and making things public. One actually important part of this is verifying things like "the package I download from what will become the public release URL has checksums that match what's in the checksum file", so it does have to actually go up on our server for that. And if we…
Will wait for the official release announcement next time. Sorry again.