Django The web framework for perfectionists with deadlines. Menu
Posted by James Bennett on January 4, 2013 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
Posted by James Bennett on October 17, 2012 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 HT
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
Posted by James Bennett on March 23, 2012 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
Posted by James Bennett on March 13, 2012 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
Posted by James Bennett on February 15, 2012 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 an
Posted by Russell Keith-Magee on January 16, 2012 The Django Software Foundation (DSF) is kicking off the new year with a corporate membership drive. Membership of the DSF is one tangible way that your company can publicly demonstrate its support for the Django project, and give back to the Open Source community that has developed Django. To kick off this membership drive, we're proud to announce
Posted by James Bennett on February 8, 2011 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
This example is for Django's SVN release, which can be significantly different from previous releases. Get old examples here: 0.96, 0.95. To define a one-to-one relationship, use OneToOneField(). In this example, a Place optionally can be a Restaurant. Model source code from django.db import models, transaction, IntegrityError class Place(models.Model): name = models.CharField(max_length=50) addr
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く