2.0.txt 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508
  1. ============================================
  2. Django 2.0 release notes - UNDER DEVELOPMENT
  3. ============================================
  4. Welcome to Django 2.0!
  5. These release notes cover the :ref:`new features <whats-new-2.0>`, as well as
  6. some :ref:`backwards incompatible changes <backwards-incompatible-2.0>` you'll
  7. want to be aware of when upgrading from Django 1.11 or earlier. We've
  8. :ref:`dropped some features<removed-features-2.0>` that have reached the end of
  9. their deprecation cycle, and we've :ref:`begun the deprecation process for some
  10. features <deprecated-features-2.0>`.
  11. See the :doc:`/howto/upgrade-version` guide if you're updating an existing
  12. project.
  13. Python compatibility
  14. ====================
  15. Django 2.0 supports Python 3.5+. Since Django 1.11, support for Python 2.7 and
  16. 3.4 is removed. We **highly recommend** and only officially support the latest
  17. release of each series.
  18. Third-party library support for older version of Django
  19. =======================================================
  20. Following the release of Django 2.0, we suggest that third-party app authors
  21. drop support for all versions of Django prior to 1.11. At that time, you should
  22. be able run your package's tests using ``python -Wd`` so that deprecation
  23. warnings do appear. After making the deprecation warning fixes, your app should
  24. be compatible with Django 2.0.
  25. .. _whats-new-2.0:
  26. What's new in Django 2.0
  27. ========================
  28. Minor features
  29. --------------
  30. :mod:`django.contrib.admin`
  31. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  32. * ...
  33. :mod:`django.contrib.admindocs`
  34. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  35. * ...
  36. :mod:`django.contrib.auth`
  37. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  38. * The default iteration count for the PBKDF2 password hasher is increased from
  39. 36,000 to 100,000.
  40. :mod:`django.contrib.contenttypes`
  41. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  42. * ...
  43. :mod:`django.contrib.gis`
  44. ~~~~~~~~~~~~~~~~~~~~~~~~~
  45. * Added MySQL support for the
  46. :class:`~django.contrib.gis.db.models.functions.AsGeoJSON` function,
  47. :class:`~django.contrib.gis.db.models.functions.GeoHash` function,
  48. :class:`~django.contrib.gis.db.models.functions.IsValid` function, and
  49. :lookup:`isvalid` lookup.
  50. * Added the :class:`~django.contrib.gis.db.models.functions.Azimuth` and
  51. :class:`~django.contrib.gis.db.models.functions.LineLocatePoint` functions,
  52. supported on PostGIS and SpatiaLite.
  53. * Any :class:`~django.contrib.gis.geos.GEOSGeometry` imported from GeoJSON now
  54. has its SRID set.
  55. :mod:`django.contrib.messages`
  56. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  57. * ...
  58. :mod:`django.contrib.postgres`
  59. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  60. * The new ``distinct`` argument for
  61. :class:`~django.contrib.postgres.aggregates.ArrayAgg` determines if
  62. concatenated values will be distinct.
  63. * The new :class:`~django.contrib.postgres.functions.RandomUUID` database
  64. function returns a version 4 UUID. It requires use of PostgreSQL's
  65. ``pgcrypto`` extension which can be activated using the new
  66. :class:`~django.contrib.postgres.operations.CryptoExtension` migration
  67. operation.
  68. :mod:`django.contrib.redirects`
  69. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  70. * ...
  71. :mod:`django.contrib.sessions`
  72. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  73. * ...
  74. :mod:`django.contrib.sitemaps`
  75. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  76. * Added the ``protocol`` keyword argument to the
  77. :class:`~django.contrib.sitemaps.GenericSitemap` constructor.
  78. :mod:`django.contrib.sites`
  79. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  80. * ...
  81. :mod:`django.contrib.staticfiles`
  82. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  83. * ...
  84. :mod:`django.contrib.syndication`
  85. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  86. * ...
  87. Cache
  88. ~~~~~
  89. * ...
  90. CSRF
  91. ~~~~
  92. * ...
  93. Database backends
  94. ~~~~~~~~~~~~~~~~~
  95. * ...
  96. Email
  97. ~~~~~
  98. * ...
  99. File Storage
  100. ~~~~~~~~~~~~
  101. * ...
  102. File Uploads
  103. ~~~~~~~~~~~~
  104. * ...
  105. Forms
  106. ~~~~~
  107. * The new ``date_attrs`` and ``time_attrs`` arguments for
  108. :class:`~django.forms.SplitDateTimeWidget` and
  109. :class:`~django.forms.SplitHiddenDateTimeWidget` allow specifying different
  110. HTML attributes for the ``DateInput`` and ``TimeInput`` (or hidden)
  111. subwidgets.
  112. * :class:`~django.forms.FloatField` and :class:`~django.forms.DecimalField`
  113. now handle :setting:`DECIMAL_SEPARATOR` and :setting:`THOUSAND_SEPARATOR`
  114. correctly when :setting:`USE_L10N` is off.
  115. Generic Views
  116. ~~~~~~~~~~~~~
  117. * ...
  118. Internationalization
  119. ~~~~~~~~~~~~~~~~~~~~
  120. * ...
  121. Management Commands
  122. ~~~~~~~~~~~~~~~~~~~
  123. * :djadmin:`inspectdb` now translates MySQL's unsigned integer columns to
  124. ``PositiveIntegerField`` or ``PositiveSmallIntegerField``.
  125. Migrations
  126. ~~~~~~~~~~
  127. * ...
  128. Models
  129. ~~~~~~
  130. * The new :class:`~django.db.models.functions.StrIndex` database function
  131. finds the starting index of a string inside another string.
  132. Requests and Responses
  133. ~~~~~~~~~~~~~~~~~~~~~~
  134. * The :djadmin:`runserver` Web server supports HTTP 1.1.
  135. Serialization
  136. ~~~~~~~~~~~~~
  137. * ...
  138. Signals
  139. ~~~~~~~
  140. * ...
  141. Templates
  142. ~~~~~~~~~
  143. * To increase the usefulness of :meth:`.Engine.get_default` in third-party
  144. apps, it now returns the first engine if multiple ``DjangoTemplates`` engines
  145. are configured in ``TEMPLATES`` rather than raising ``ImproperlyConfigured``.
  146. Tests
  147. ~~~~~
  148. * Added threading support to :class:`~django.test.LiveServerTestCase`.
  149. URLs
  150. ~~~~
  151. * ...
  152. Validators
  153. ~~~~~~~~~~
  154. * ...
  155. .. _backwards-incompatible-2.0:
  156. Backwards incompatible changes in 2.0
  157. =====================================
  158. Removed support for bytestrings in some places
  159. ----------------------------------------------
  160. To support native Python 2 strings, older Django versions had to accept both
  161. bytestrings and unicode strings. Now that Python 2 support is dropped,
  162. bytestrings should only be encountered around input/output boundaries (handling
  163. of binary fields or HTTP streams, for example). You might have to update your
  164. code to limit bytestring usage to a minimum, as Django no longer accepts
  165. bytestrings in certain code paths.
  166. Database backend API
  167. --------------------
  168. * The ``DatabaseOperations.datetime_cast_date_sql()``,
  169. ``datetime_cast_time_sql()``, ``datetime_trunc_sql()``, and
  170. ``datetime_extract_sql()`` methods now return only the SQL to perform the
  171. operation instead of SQL and a list of parameters.
  172. Dropped support for Oracle 11.2
  173. -------------------------------
  174. The end of upstream support for Oracle 11.2 is Dec. 2020. Django 1.11 will be
  175. supported until April 2020 which almost reaches this date. Django 2.0
  176. officially supports Oracle 12.1+.
  177. Default MySQL isolation level is read committed
  178. -----------------------------------------------
  179. MySQL's default isolation level, repeatable read, may cause data loss in
  180. typical Django usage. To prevent that and for consistency with other databases,
  181. the default isolation level is now read committed. You can use the
  182. :setting:`DATABASES` setting to :ref:`use a different isolation level
  183. <mysql-isolation-level>`, if needed.
  184. :attr:`AbstractUser.last_name <django.contrib.auth.models.User.last_name>` ``max_length`` increased to 150
  185. ----------------------------------------------------------------------------------------------------------
  186. A migration for :attr:`django.contrib.auth.models.User.last_name` is included.
  187. If you have a custom user model inheriting from ``AbstractUser``, you'll need
  188. to generate and apply a database migration for your user model.
  189. If you want to preserve the 30 character limit for last names, use a custom
  190. form::
  191. from django.contrib.auth.forms import UserChangeForm
  192. class MyUserChangeForm(UserChangeForm):
  193. last_name = forms.CharField(max_length=30, required=False)
  194. If you wish to keep this restriction in the admin when editing users, set
  195. ``UserAdmin.form`` to use this form::
  196. from django.contrib.auth.admin import UserAdmin
  197. from django.contrib.auth.models import User
  198. class MyUserAdmin(UserAdmin):
  199. form = MyUserChangeForm
  200. admin.site.unregister(User)
  201. admin.site.register(User, MyUserAdmin)
  202. Miscellaneous
  203. -------------
  204. * The ``SessionAuthenticationMiddleware`` class is removed. It provided no
  205. functionality since session authentication is unconditionally enabled in
  206. Django 1.10.
  207. * The default HTTP error handlers (``handler404``, etc.) are now callables
  208. instead of dotted Python path strings. Django favors callable references
  209. since they provide better performance and debugging experience.
  210. * :class:`~django.views.generic.base.RedirectView` no longer silences
  211. ``NoReverseMatch`` if the ``pattern_name`` doesn't exist.
  212. .. _deprecated-features-2.0:
  213. Features deprecated in 2.0
  214. ==========================
  215. Miscellaneous
  216. -------------
  217. * The ``django.db.backends.postgresql_psycopg2`` module is deprecated in favor
  218. of ``django.db.backends.postgresql``. It's been an alias since Django 1.9.
  219. This only affects code that imports from the module directly. The
  220. ``DATABASES`` setting can still use
  221. ``'django.db.backends.postgresql_psycopg2'``, though you can simplify that by
  222. using the ``'django.db.backends.postgresql'`` name added in Django 1.9.
  223. * ``django.shortcuts.render_to_response()`` is deprecated in favor of
  224. :func:`django.shortcuts.render`. ``render()`` takes the same arguments
  225. except that is also requires a ``request``.
  226. * The ``DEFAULT_CONTENT_TYPE`` setting is deprecated. It doesn't interact well
  227. well with third-party apps and is obsolete since HTML5 has mostly superseded
  228. XHTML.
  229. * ``HttpRequest.xreadlines()`` is deprecated in favor of iterating over the
  230. request.
  231. .. _removed-features-2.0:
  232. Features removed in 2.0
  233. =======================
  234. These features have reached the end of their deprecation cycle and are removed
  235. in Django 2.0. See :ref:`deprecated-features-1.9` and
  236. :ref:`deprecated-features-1.10` for details, including how to remove usage of
  237. these features.
  238. * The ``weak`` argument to ``django.dispatch.signals.Signal.disconnect()`` is
  239. removed.
  240. * ``django.db.backends.base.BaseDatabaseOperations.check_aggregate_support()``
  241. is removed.
  242. * The ``django.forms.extras`` package is removed.
  243. * The ``assignment_tag`` helper is removed.
  244. * The ``host`` argument to ``SimpleTestCase.assertsRedirects()`` is removed.
  245. The compatibility layer which allows absolute URLs to be considered equal to
  246. relative ones when the path is identical is also removed.
  247. * ``Field.rel`` and ``Field.remote_field.to`` are removed.
  248. * The ``on_delete`` argument for ``ForeignKey`` and ``OneToOneField`` are now
  249. required.
  250. * ``django.db.models.fields.add_lazy_relation()`` is removed.
  251. * When time zone support is enabled, database backends that don't support time
  252. zones no longer convert aware datetimes to naive values in UTC anymore when
  253. such values are passed as parameters to SQL queries executed outside of the
  254. ORM, e.g. with ``cursor.execute()``.
  255. * ``django.contrib.auth.tests.utils.skipIfCustomUser()`` is removed.
  256. * The ``GeoManager`` and ``GeoQuerySet`` classes are removed.
  257. * The ``django.contrib.gis.geoip`` module is removed.
  258. * The ``supports_recursion`` check for template loaders is removed from:
  259. * ``django.template.engine.Engine.find_template()``
  260. * ``django.template.loader_tags.ExtendsNode.find_template()``
  261. * ``django.template.loaders.base.Loader.supports_recursion()``
  262. * ``django.template.loaders.cached.Loader.supports_recursion()``
  263. * The ``load_template`` and ``load_template_sources`` template loader methods
  264. are removed.
  265. * The ``template_dirs`` argument for template loaders is removed:
  266. * ``django.template.loaders.base.Loader.get_template()``
  267. * ``django.template.loaders.cached.Loader.cache_key()``
  268. * ``django.template.loaders.cached.Loader.get_template()``
  269. * ``django.template.loaders.cached.Loader.get_template_sources()``
  270. * ``django.template.loaders.filesystem.Loader.get_template_sources()``
  271. * ``django.template.loaders.base.Loader.__call__()`` is removed.
  272. * Support for custom error views that don't accept an ``exception`` parameter
  273. is removed.
  274. * The ``mime_type`` attribute of ``django.utils.feedgenerator.Atom1Feed`` and
  275. ``django.utils.feedgenerator.RssFeed`` is removed.
  276. * The ``app_name`` argument to ``include()`` is removed.
  277. * Support for passing a 3-tuple (including ``admin.site.urls``) as the first
  278. argument to ``include()`` is removed.
  279. * Support for setting a URL instance namespace without an application namespace
  280. is removed.
  281. * ``Field._get_val_from_obj()`` is removed.
  282. * ``django.template.loaders.eggs.Loader`` is removed.
  283. * The ``current_app`` parameter to the ``contrib.auth`` function-based views is
  284. removed.
  285. * The ``callable_obj`` keyword argument to
  286. ``SimpleTestCase.assertRaisesMessage()`` is removed.
  287. * Support for the ``allow_tags`` attribute on ``ModelAdmin`` methods is
  288. removed.
  289. * The ``enclosure`` keyword argument to ``SyndicationFeed.add_item()`` is
  290. removed.
  291. * The ``django.template.loader.LoaderOrigin`` and
  292. ``django.template.base.StringOrigin`` aliases for
  293. ``django.template.base.Origin`` are removed.
  294. * The ``makemigrations --exit`` option is removed.
  295. * Support for direct assignment to a reverse foreign key or many-to-many
  296. relation is removed.
  297. * The ``get_srid()`` and ``set_srid()`` methods of
  298. ``django.contrib.gis.geos.GEOSGeometry`` are removed.
  299. * The ``get_x()``, ``set_x()``, ``get_y()``, ``set_y()``, ``get_z()``, and
  300. ``set_z()`` methods of ``django.contrib.gis.geos.Point`` are removed.
  301. * The ``get_coords()`` and ``set_coords()`` methods of
  302. ``django.contrib.gis.geos.Point`` are removed.
  303. * The ``cascaded_union`` property of ``django.contrib.gis.geos.MultiPolygon``
  304. is removed.
  305. * ``django.utils.functional.allow_lazy()`` is removed.
  306. * The ``shell --plain`` option is removed.
  307. * The ``django.core.urlresolvers`` module is removed.
  308. * ``CommaSeparatedIntegerField`` is removed, except for support in historical
  309. migrations.
  310. * The template ``Context.has_key()`` method is removed.
  311. * Support for the ``django.core.files.storage.Storage.accessed_time()``,
  312. ``created_time()``, and ``modified_time()`` methods is removed.
  313. * Support for query lookups using the model name when
  314. ``Meta.default_related_name`` is set is removed.
  315. * The MySQL ``__search`` lookup is removed.
  316. * The shim for supporting custom related manager classes without a
  317. ``_apply_rel_filters()`` method is removed.
  318. * Using ``User.is_authenticated()`` and ``User.is_anonymous()`` as methods
  319. rather than properties is no longer supported.
  320. * The ``Model._meta.virtual_fields`` attribute is removed.
  321. * The keyword arguments ``virtual_only`` in ``Field.contribute_to_class()`` and
  322. ``virtual`` in ``Model._meta.add_field()`` are removed.
  323. * The ``javascript_catalog()`` and ``json_catalog()`` views are removed.
  324. * ``django.contrib.gis.utils.precision_wkt()`` is removed.
  325. * In multi-table inheritance, implicit promotion of a ``OneToOneField`` to a
  326. ``parent_link`` is removed.
  327. * Support for ``Widget._format_value()`` is removed.
  328. * ``FileField`` methods ``get_directory_name()`` and ``get_filename()`` are
  329. removed.
  330. * The ``mark_for_escaping()`` function and the classes it uses: ``EscapeData``,
  331. ``EscapeBytes``, ``EscapeText``, ``EscapeString``, and ``EscapeUnicode`` are
  332. removed.
  333. * The ``escape`` filter now uses ``django.utils.html.conditional_escape()``.
  334. * ``Manager.use_for_related_fields`` is removed.
  335. * Model ``Manager`` inheritance follows MRO inheritance rules. The requirement
  336. to use ``Meta.manager_inheritance_from_future`` to opt-in to the behavior is
  337. removed.
  338. * Support for old-style middleware using ``settings.MIDDLEWARE_CLASSES`` is
  339. removed.