はてなブックマーク

The Django team is happy to announce the release of Django 2.1. The release notes cover the smorgasbord of new features in detail, the model “view” permission is a highlight that many will appreciate. You can get Django 2.1 from our downloads page or from the Python Package Index. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252. With the release of Django 2.1, Django 2.0 has r

The Django team is happy to announce the release of Django 2.0. This release starts Django’s use of a loose form of semantic versioning, but there aren’t any major backwards incompatible changes (except that support for Python 2.7 is removed) that might be expected of a 2.0 release. Upgrading should be a similar amount of effort as past feature releases. The release notes cover the assortment of n

Django 2.0 alpha 1 is now available. It represents the first stage in the 2.0 release cycle and is an opportunity for you to try out the changes coming in Django 2.0. Django 2.0 has an assortment of new features which you can read about in the in-development 2.0 release notes. This alpha milestone marks a complete feature freeze. The current release schedule calls for a beta release in about a mon

Posted by Andrew Godwin on September 9, 2016 The Django team is pleased to announce that the Channels project is now officially part of the Django project, under our new Official Projects program. Channels is the effort to bring WebSockets, long-poll HTTP, and other non-request-response protocol and business logic handling to Django, as part of our ongoing effort to establish what makes a useful w

After more than a year of development, the Django team is happy to announce the release of Django 1.8 according to schedule. This version has been designated as a long-term support (LTS) release, which means that security and data loss fixes will be applied for at least the next three years. As always, the release notes cover everything in-depth, but some of the major highlights are: Native suppor

Posted by Jannis Leidel and Russell Keith-Magee on Dec. 15, 2014 The Django project is excited to announce that after many years, we're launching a redesign of our primary website, our documentation site and our issue tracker. Django's website has been largely unchanged since the project was launched back in 2005, so you can imagine how excited we are to update it. The original design was created

It's here! After nearly a year of development, today we're proud to announce the release of Django 1.7. As always, the release notes cover everything in-depth, but some of the major highlights of Django 1.7 are: A new built-in database migration system. Notes on upgrading from South (a popular third-party application providing migration functionality) are also available. A refactored concept of Dj

Today the Django team is issuing multiple releases -- Django 1.4.13, Django 1.5.8, Django 1.6.5 and Django 1.7 beta 4 -- as part of our security process. These releases are now available on PyPI and our download page. These releases address a caching issue which might lead to cache poisoning and an incorrect validation of safe redirect targets. Since these issues will affect the majority of users

This one's for Malcolm Earlier this year, the Django community lost a member, a developer and a friend; Malcolm Tredinnick was a long-time contributor to many open-source projects, including Django, where he served as a committer from 2006 onward. More importantly, he was a brilliant mind, a beloved and respected member of our community, a patient mentor and a dear friend. The news of his passing,

At last week's Black Hat conference, researchers announced the BREACH attack, a new attack on web apps that can recover data even when secured with SSL connections. The BREACH paper (PDF) contains full details (and is a good and fairly easy read). Given what we know so far, we believe that BREACH may be used to compromise Django's CSRF protection. Thus, we're issuing this advisory so that our user

Hello fellow Djangonauts, We have difficult news: Malcolm Tredinnick has passed away. Malcolm was a long-time contributor to Django, a model community member, a brilliant mind, and a friend. His contributions to Django — and to many other open source projects — are nearly impossible to enumerate. Many on the core Django team had their first patches reviewed by him; his mentorship enriched us. His

It's here! After quite a lot of work, today we're proud to announce the release of Django 1.5. As always, the release notes cover all the good stuff in detail, but since this is a pretty big release let's take a look at some of the highlights: Django 1.5 introduces support for a configurable User model. The basic Django User model is still around, of course, but now there's first-class support for

As part of the Django 1.5 release process, today we've released Django 1.5 release candidate 1, a preview/testing package for Django 1.5. As with all pre-release packages, this is not for production use, but if you'd like to try out some of the new goodies coming in 1.5, or if you'd like to pitch in and help us fix bugs before the final 1.5 release, feel free to grab a copy and give it a spin. In

As part of the Django 1.5 release process, today we've released Django 1.5 beta 1, a preview/testing package that gives a little taste of some of the new stuff coming in Django 1.5. As with all alpha and beta packages, this is not for production use, but if you'd like to try out some of the new goodies coming in 1.5, or if you'd like to pitch in and help us fix bugs before the final 1.5 release (d

Today the Django team is issuing multiple releases -- Django 1.3.4 and Django 1.4.2 -- to remedy security issues reported to us. All users are encouraged to upgrade Django immediately. Host header poisoning Some parts of Django -- independent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host header. Some attacks against this ar

A little bit of history In May, Vinay Sajip published a fork proving that it was possible to support both Python 2 and 3 with a single codebase, and pass the entire test suite. This fork built upon earlier efforts by Martin von Löwis. Shortly after, the core team decided to use six as a compatibility layer, rather than an ad-hoc library. The goal was not only to cover Django's needs, but also to c

Building the Django Community for 19 years, 11 months. Come join us! Django People Django People was a geographical community site for Django developers. It was sunset in September 2020. Please head over to the Community page to find support resources and how to get involved. Back to Top More Help Frequently Asked Questions The FAQ answers many common questions r/Django Subreddit News and links on

It's here! After many months of work, we're proud to announce the release today of Django 1.4. There's plenty of cool stuff in this release, and the release notes cover it all in detail. You can also swing by the downloads page to grab a copy of the release package. And as always, signed checksums for the release package are available. One important point is worth mentioning here, however: Django

With Django 1.4 so close to release, it's also time to start talking about Django 1.5. Not many details have been finalized, but one very important announcement was made Sunday during the PyCon lightning talks session. Perhaps the most common question about Django's future, for some time now, has been "when will Django support Python 3?" The answer is that porting code is relatively straightforwar

As part of the Django 1.4 release process, tonight we've released Django 1.4 beta 1, a preview/testing package that gives a little taste of some of the new features coming in Django 1.4. As with all alpha and beta packages, this is not for production use, but if you'd like to try out some of the new goodies coming in 1.4, or if you'd like to pitch in and help us fix bugs before the final 1.4 relea

Today the Django team is issuing multiple releases -- Django 1.2.6 and Django 1.3.1 -- to remedy security issues reported to us. Additionally, this announcement contains advisories for several other issues which, while not requiring changes to Django itself, will be of concern to users of Django. All users are encouraged to upgrade Django, and to implement the recommendations in these advisories,

Today the Django team is issuing multiple releases -- Django 1.2.5 and Django 1.1.4 -- to remedy three security issues reported to us. All users of affected versions of Django are urged to upgrade immediately. Flaw in CSRF handling Django includes a CSRF-protection mechanism, which makes use of a token inserted into outgoing forms. Middleware then checks for the token's presence on form submission

Posted by Russell Keith-Magee on Oct. 25, 2010 Astute observers will have noted that October 18 has come and gone, but Django 1.3 alpha 1 hasn't been released. There are two reasons for this. Firstly, we landed a number of big features very close to the original planned release date, including class-based views, a static media framework, and a context manager for transactions. However, we're still

Django 1.2 has been in the wild for a couple of months, and we've had plenty of time to talk about what we want to see in Django 1.3. That means it's time to pick features and nominate some deadlines. From the feedback from DjangoCon, and from conversations on the mailing lists and IRC, it's fairly clear that people are happy with the new features that have been added with Django 1.1 and 1.2. Howe

It's here! After many months of work, we're proud to announce the release today of Django 1.2. There's so much cool stuff packed into it that even a summary can't do it justice; you'll just have to go read the release notes to see it all, then swing by the downloads page to grab a copy. And as always, signed checksums for the release package are available. One important point is worth mentioning h

Today the Django project is issuing a set of releases to remedy a security issue. This issue was disclosed publicly by a third party on a high-traffic mailing list, and attempts have been made to exploit it against live Django installations; as such, we are bypassing our normal policy for security disclosure and immediately issuing patches and updated releases. Description of vulnerability Django'