<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Django 1.0 beta 1 release notes — Django v1.2 documentation</title>
<link rel="stylesheet" href="../_static/default.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '1.2',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<link rel="top" title="Django v1.2 documentation" href="../index.html" />
<link rel="up" title="Release notes" href="index.html" />
<link rel="next" title="Django 1.0 alpha 2 release notes" href="1.0-alpha-2.html" />
<link rel="prev" title="Django 1.0 beta 2 release notes" href="1.0-beta-2.html" />
<script type="text/javascript" src="../templatebuiltins.js"></script>
<script type="text/javascript">
(function($) {
if (!django_template_builtins) {
// templatebuiltins.js missing, do nothing.
return;
}
$(document).ready(function() {
// Hyperlink Django template tags and filters
var base = "../ref/templates/builtins.html";
if (base == "#") {
// Special case for builtins.html itself
base = "";
}
// Tags are keywords, class '.k'
$("div.highlight\\-html\\+django span.k").each(function(i, elem) {
var tagname = $(elem).text();
if ($.inArray(tagname, django_template_builtins.ttags) != -1) {
var fragment = tagname.replace(/_/, '-');
$(elem).html("<a href='" + base + "#" + fragment + "'>" + tagname + "</a>");
}
});
// Filters are functions, class '.nf'
$("div.highlight\\-html\\+django span.nf").each(function(i, elem) {
var filtername = $(elem).text();
if ($.inArray(filtername, django_template_builtins.tfilters) != -1) {
var fragment = filtername.replace(/_/, '-');
$(elem).html("<a href='" + base + "#" + fragment + "'>" + filtername + "</a>");
}
});
});
})(jQuery);
</script>
</head>
<body>
<div class="document">
<div id="custom-doc" class="yui-t6">
<div id="hd">
<h1><a href="../index.html">Django v1.2 documentation</a></h1>
<div id="global-nav">
<a title="Home page" href="../index.html">Home</a> |
<a title="Table of contents" href="../contents.html">Table of contents</a> |
<a title="Global index" href="../genindex.html">Index</a> |
<a title="Module index" href="../py-modindex.html">Modules</a>
</div>
<div class="nav">
« <a href="1.0-beta-2.html" title="Django 1.0 beta 2 release notes">previous</a>
|
<a href="index.html" title="Release notes" accesskey="U">up</a>
|
<a href="1.0-alpha-2.html" title="Django 1.0 alpha 2 release notes">next</a> »</div>
</div>
<div id="bd">
<div id="yui-main">
<div class="yui-b">
<div class="yui-g" id="releases-1.0-beta">
<div class="section" id="s-django-1-0-beta-1-release-notes">
<span id="django-1-0-beta-1-release-notes"></span><h1>Django 1.0 beta 1 release notes<a class="headerlink" href="#django-1-0-beta-1-release-notes" title="Permalink to this headline">¶</a></h1>
<p>Welcome to Django 1.0 beta 1!</p>
<p>This is the third in a series of preview/development releases leading
up to the eventual release of Django 1.0, currently scheduled to take
place in early September 2008. This releases is primarily targeted at
developers who are interested in testing the Django codebase and
helping to identify and resolve bugs prior to the final 1.0 release.</p>
<p>As such, this release is <em>not</em> intended for production use, and any
such use is discouraged.</p>
<div class="section" id="s-what-s-new-in-django-1-0-beta-1">
<span id="what-s-new-in-django-1-0-beta-1"></span><h2>What’s new in Django 1.0 beta 1<a class="headerlink" href="#what-s-new-in-django-1-0-beta-1" title="Permalink to this headline">¶</a></h2>
<p>Django’s development trunk has been the site of nearly constant activity over
the past year, with several major new features landing since the 0.96 release.
For features which were new as of Django 1.0 alpha 1, see <a class="reference internal" href="1.0-alpha-1.html"><em>the 1.0 alpha 1
release notes</em></a>. For features which were new as of Django
1.0 alpha 2, see <a class="reference internal" href="1.0-alpha-2.html"><em>the 1.0 alpha 2 release notes</em></a>.</p>
<p>This beta release does not contain any major new features, but does
include several smaller updates and improvements to Django:</p>
<dl class="docutils">
<dt>Generic relations in forms and admin</dt>
<dd>Classes are now included in <tt class="docutils literal"><span class="pre">django.contrib.contenttypes</span></tt> which
can be used to support generic relations in both the admin
interface and in end-user forms. See <a class="reference internal" href="../ref/contrib/contenttypes.html#generic-relations"><em>the documentation for
generic relations</em></a> for details.</dd>
<dt>Improved flexibility in the admin</dt>
<dd>Following up on the refactoring of Django’s administrative
interface (<tt class="docutils literal"><span class="pre">django.contrib.admin</span></tt>), introduced in Django 1.0
alpha 1, two new hooks have been added to allow customized pre-
and post-save handling of model instances in the admin. Full
details are in <a class="reference internal" href="../ref/contrib/admin/index.html"><em>the admin documentation</em></a>.</dd>
<dt><tt class="docutils literal"><span class="pre">INSERT</span></tt>/<tt class="docutils literal"><span class="pre">UPDATE</span></tt> distinction</dt>
<dd>Although Django’s default behavior of having a model’s <tt class="docutils literal"><span class="pre">save()</span></tt>
method automatically determine whether to perform an <tt class="docutils literal"><span class="pre">INSERT</span></tt> or
an <tt class="docutils literal"><span class="pre">UPDATE</span></tt> at the SQL level is suitable for the majority of
cases, there are occasional situations where forcing one or the
other is useful. As a result, models can now support an additional
parameter to <tt class="docutils literal"><span class="pre">save()</span></tt> which can force a specific
operation. Consult the database API documentation for details
and important notes about appropriate use of this parameter.</dd>
<dt>Split <tt class="docutils literal"><span class="pre">CacheMiddleware</span></tt></dt>
<dd>Django’s <tt class="docutils literal"><span class="pre">CacheMiddleware</span></tt> has been split into three classes:
<tt class="docutils literal"><span class="pre">CacheMiddleware</span></tt> itself still exists and retains all of its
previous functionality, but it is now built from two separate
middleware classes which handle the two parts of caching (inserting
into and reading from the cache) separately, offering additional
flexibility for situations where combining these functions into a
single middleware posed problems. Full details, including updated
notes on appropriate use, are in
<a class="reference internal" href="../topics/cache.html"><em>the caching documentation</em></a>.</dd>
<dt>Removal of deprecated features</dt>
<dd>A number of features and methods which had previously been marked
as deprecated, and which were scheduled for removal prior to the
1.0 release, are no longer present in Django. These include
imports of the form library from <tt class="docutils literal"><span class="pre">django.newforms</span></tt> (now located
simply at <tt class="docutils literal"><span class="pre">django.forms</span></tt>), the <tt class="docutils literal"><span class="pre">form_for_model</span></tt> and
<tt class="docutils literal"><span class="pre">form_for_instance</span></tt> helper functions (which have been replaced
by <tt class="docutils literal"><span class="pre">ModelForm</span></tt>) and a number of deprecated features which were
replaced by the dispatcher, file-uploading and file-storage
refactorings introduced in the Django 1.0 alpha releases. A full
list of these and all other backwards-incompatible changes is
available on <a class="reference external" href="http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Removedseveralmoredeprecatedfeaturesfor1.0">the Django wiki</a>.</dd>
</dl>
<p>A number of other improvements and bugfixes have also been included:
some tricky cases involving case-sensitivity in differing MySQL
collations have been resolved, Windows packaging and installation has
been improved and the method by which Django generates unique session
identifiers has been made much more robust.</p>
</div>
<div class="section" id="s-the-django-1-0-roadmap">
<span id="the-django-1-0-roadmap"></span><h2>The Django 1.0 roadmap<a class="headerlink" href="#the-django-1-0-roadmap" title="Permalink to this headline">¶</a></h2>
<p>One of the primary goals of this beta release is to focus attention on
the remaining features to be implemented for Django 1.0, and on the
bugs that need to be resolved before the final release. Following this
release, we’ll be conducting a series of development sprints building
up to the release-candidate stage, followed soon after by Django
1.0. The timeline is projected to be:</p>
<ul class="simple">
<li>August 15, 2008: Sprint (based in Austin, Texas, USA, and online).</li>
<li>August 17, 2008: Sprint (based in Tel Aviv, Israel, and online).</li>
<li><strong>August 21, 2008: Django 1.0 release candidate 1.</strong> At this point,
all strings marked for translation within Django’s codebase will be
frozen, to provide contributors time to check and finalize all of
Django’s bundled translation files prior to the final 1.0 release.</li>
<li>August 22, 2008: Sprint (based in Portland, Oregon, USA, and online).</li>
<li><strong>August 26, 2008: Django 1.0 release candidate 2.</strong></li>
<li>August 30, 2008: Sprint (based in London, England, UK, and online).</li>
<li><strong>September 2, 2008: Django 1.0 final release.</strong> The official Django
1.0 release party will take place during the first-ever DjangoCon,
to be held in Mountain View, California, USA, September 6-7.</li>
</ul>
<p>Of course, like any estimated timeline, this is subject to change as
requirements dictate. The latest information will always be available
on the Django project wiki:</p>
<blockquote>
<div><a class="reference external" href="http://code.djangoproject.com/wiki/VersionOneRoadmap">http://code.djangoproject.com/wiki/VersionOneRoadmap</a></div></blockquote>
</div>
<div class="section" id="s-what-you-can-do-to-help">
<span id="what-you-can-do-to-help"></span><h2>What you can do to help<a class="headerlink" href="#what-you-can-do-to-help" title="Permalink to this headline">¶</a></h2>
<p>In order to provide a high-quality 1.0 release, we need your
help. Although this beta release is, again, <em>not</em> intended for
production use, you can help the Django team by trying out the beta
codebase in a safe test environment and reporting any bugs or issues
you encounter. The Django ticket tracker is the central place to
search for open issues:</p>
<blockquote>
<div><a class="reference external" href="http://code.djangoproject.com/timeline">http://code.djangoproject.com/timeline</a></div></blockquote>
<p>Please open new tickets if no existing ticket corresponds to a problem
you’re running into.</p>
<p>Additionally, discussion of Django development, including progress
toward the 1.0 release, takes place daily on the django-developers
mailing list:</p>
<blockquote>
<div><a class="reference external" href="http://groups.google.com/group/django-developers">http://groups.google.com/group/django-developers</a></div></blockquote>
<p>...and in the <tt class="docutils literal"><span class="pre">#django-dev</span></tt> IRC channel on <tt class="docutils literal"><span class="pre">irc.freenode.net</span></tt>. If
you’re interested in helping out with Django’s development, feel free
to join the discussions there.</p>
<p>Django’s online documentation also includes pointers on how to
contribute to Django:</p>
<blockquote>
<div><a class="reference internal" href="../internals/contributing.html"><em>contributing to Django</em></a></div></blockquote>
<p>Contributions on any level – developing code, writing
documentation or simply triaging tickets and helping to test proposed
bugfixes – are always welcome and appreciated.</p>
</div>
</div>
</div>
</div>
</div>
<div class="yui-b" id="sidebar">
<div class="sphinxsidebar">
<div class="sphinxsidebarwrapper">
<h3><a href="../contents.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Django 1.0 beta 1 release notes</a><ul>
<li><a class="reference internal" href="#what-s-new-in-django-1-0-beta-1">What’s new in Django 1.0 beta 1</a></li>
<li><a class="reference internal" href="#the-django-1-0-roadmap">The Django 1.0 roadmap</a></li>
<li><a class="reference internal" href="#what-you-can-do-to-help">What you can do to help</a></li>
</ul>
</li>
</ul>
<h3>Browse</h3>
<ul>
<li>Prev: <a href="1.0-beta-2.html">Django 1.0 beta 2 release notes</a></li>
<li>Next: <a href="1.0-alpha-2.html">Django 1.0 alpha 2 release notes</a></li>
</ul>
<h3>You are here:</h3>
<ul>
<li>
<a href="../index.html">Django v1.2 documentation</a>
<ul><li><a href="index.html">Release notes</a>
<ul><li>Django 1.0 beta 1 release notes</li></ul>
</li></ul>
</li>
</ul>
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="../_sources/releases/1.0-beta.txt"
rel="nofollow">Show Source</a></li>
</ul>
<div id="searchbox" style="display: none">
<h3>Quick search</h3>
<form class="search" action="../search.html" method="get">
<input type="text" name="q" size="18" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<h3>Last update:</h3>
<p class="topless">Jan 28, 2011</p>
</div>
</div>
<div id="ft">
<div class="nav">
« <a href="1.0-beta-2.html" title="Django 1.0 beta 2 release notes">previous</a>
|
<a href="index.html" title="Release notes" accesskey="U">up</a>
|
<a href="1.0-alpha-2.html" title="Django 1.0 alpha 2 release notes">next</a> »</div>
</div>
</div>
<div class="clearer"></div>
</div>
</body>
</html>
distrib
>
Mandriva
>
2010.1
>
x86_64
>
media
>
main-backports
>
by-pkgid
>
bc8a726fff5aedb19088c6244d3dd008
>
files
>
2889
