{"title":"Django 1.0.1 release notes","version":"dev","locale":"en","docname":"releases/1.0.1","url":"/en/dev/releases/1.0.1/","canonical":"https://djangodocs.dev/en/dev/releases/1.0.1/","summary":"Welcome to Django 1.0.1! This is the first “bugfix” release in the Django 1.0 series, improving the stability and performance of the Django 1.0 codebase.","html":"<h1>Django 1.0.1 release notes<a class=\"heading-anchor\" href=\"#django-1-0-1-release-notes\"><span class=\"visually-hidden\">Link to this heading</span><span aria-hidden=\"true\">#</span></a></h1>\n<p>Welcome to Django 1.0.1!</p>\n<p>This is the first “bugfix” release in the Django 1.0 series, improving\nthe stability and performance of the Django 1.0 codebase. As such,\nDjango 1.0.1 contains no new features (and, pursuant to <a class=\"reference internal\" href=\"/en/dev/misc/api-stability/\"><span class=\"doc\">our\ncompatibility policy</span></a>, maintains backwards\ncompatibility with Django 1.0), but does contain a number of fixes\nand other improvements. Django 1.0.1 is a recommended upgrade for any\ndevelopment or deployment currently using or targeting Django 1.0.</p>\n<section id=\"fixes-and-improvements-in-django-1-0-1\">\n<h2>Fixes and improvements in Django 1.0.1<a class=\"heading-anchor\" href=\"#fixes-and-improvements-in-django-1-0-1\"><span class=\"visually-hidden\">Link to this heading</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>Django 1.0.1 contains over two hundred fixes to the original Django\n1.0 codebase; full details of every fix are available in <a class=\"reference external\" href=\"https://github.com/django/django/commits/stable/1.0.x\">the\nhistory of the 1.0.X branch</a>, but here are some of the\nhighlights:</p>\n<ul class=\"simple\">\n<li><p>Several fixes in <code class=\"docutils literal notranslate\">django.contrib.comments</code>, pertaining to RSS\nfeeds of comments, default ordering of comments and the XHTML and\ninternationalization of the default templates for comments.</p></li>\n<li><p>Multiple fixes for Django’s support of Oracle databases, including\npagination support for GIS QuerySets, more efficient slicing of\nresults and improved introspection of existing databases.</p></li>\n<li><p>Several fixes for query support in the Django object-relational\nmapper, including repeated setting and resetting of ordering and\nfixes for working with <code class=\"docutils literal notranslate\">INSERT</code>-only queries.</p></li>\n<li><p>Multiple fixes for inline forms in formsets.</p></li>\n<li><p>Multiple fixes for <code class=\"docutils literal notranslate\">unique</code> and <code class=\"docutils literal notranslate\">unique_together</code> model\nconstraints in automatically-generated forms.</p></li>\n<li><p>Fixed support for custom callable <code class=\"docutils literal notranslate\">upload_to</code> declarations when\nhandling file uploads through automatically-generated forms.</p></li>\n<li><p>Fixed support for sorting an admin change list based on a callable\nattributes in <code class=\"docutils literal notranslate\">list_display</code>.</p></li>\n<li><p>A fix to the application of autoescaping for literal strings passed\nto the <code class=\"docutils literal notranslate\">join</code> template filter. Previously, literal strings passed\nto <code class=\"docutils literal notranslate\">join</code> were automatically escaped, contrary to <a class=\"reference internal\" href=\"/en/dev/ref/templates/language/#string-literals-and-automatic-escaping\"><span class=\"std std-ref\">the\ndocumented behavior for autoescaping and literal strings</span></a>. Literal strings\npassed to <code class=\"docutils literal notranslate\">join</code> are no longer automatically escaped, meaning you\nmust now manually escape them; this is an incompatibility if you\nwere relying on this bug, but not if you were relying on escaping\nbehaving as documented.</p></li>\n<li><p>Improved and expanded translation files for many of the languages\nDjango supports by default.</p></li>\n<li><p>And as always, a large number of improvements to Django’s\ndocumentation, including both corrections to existing documents and\nexpanded and new documentation.</p></li>\n</ul>\n</section>","rootId":"django-1-0-1-release-notes","toc":[{"title":"Fixes and improvements in Django 1.0.1","anchor":"fixes-and-improvements-in-django-1-0-1","children":[]}],"breadcrumbs":[{"docname":"releases/index","title":"Release notes","url":"/en/dev/releases/"}],"prev":{"docname":"releases/1.0.2","title":"Django 1.0.2 release notes","url":"/en/dev/releases/1.0.2/"},"next":{"docname":"releases/1.0","title":"Django 1.0 release notes","url":"/en/dev/releases/1.0/"},"formats":{"html":"/en/dev/releases/1.0.1/","markdown":"/en/dev/releases/1.0.1.md","json":"/en/dev/releases/1.0.1.json"},"source":"https://github.com/django/django/blob/main/docs/releases/1.0.1.txt","official":"https://docs.djangoproject.com/en/dev/releases/1.0.1/","inVersions":["dev","6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10","1.9","1.8"],"inLocales":["en"]}