PageRenderTime 45ms CodeModel.GetById 18ms RepoModel.GetById 1ms app.codeStats 0ms

/docs/releases/1.2-beta-1.txt

https://code.google.com/p/mango-py/
Plain Text | 173 lines | 122 code | 51 blank | 0 comment | 0 complexity | 4c637b3ea89922c98a48bef06ce42f9a MD5 | raw file
Possible License(s): BSD-3-Clause
  1. ===============================
  2. Django 1.2 beta 1 release notes
  3. ===============================
  4. February 5, 2010
  5. Welcome to Django 1.2 beta 1!
  6. This is the second in a series of preview/development releases leading
  7. up to the eventual release of Django 1.2, currently scheduled to take
  8. place in March 2010. This release is primarily targeted at developers
  9. who are interested in trying out new features and testing the Django
  10. codebase to help identify and resolve bugs prior to the final 1.2
  11. release.
  12. As such, this release is *not* intended for production use, and any
  13. such use is discouraged.
  14. This document covers changes since the Django 1.2 alpha release; the
  15. :doc:`1.2 alpha release notes </releases/1.2-alpha-1>` cover new and
  16. updated features in Django between 1.1 and 1.2 alpha.
  17. Deprecations and other changes in 1.2 beta
  18. ==========================================
  19. This beta release deprecates two portions of public API, and
  20. introduces a potentially backwards-incompatible change to
  21. another. Under :doc:`our API stability policy </misc/api-stability>`,
  22. deprecation proceeds over multiple release cycles: initially, the
  23. deprecated API will raise ``PendingDeprecationWarning``, followed by
  24. raising ``DeprecationWarning`` in the next release, and finally
  25. removal of the deprecated API in the release after that. APIs
  26. beginning the deprecation process in Django 1.2 will be removed in the
  27. Django 1.4 release.
  28. Unit test runners
  29. -----------------
  30. Django 1.2 changes the test runner tools to use a class-based
  31. approach. Old style function-based test runners will still work, but
  32. should be updated to use the new :ref:`class-based runners
  33. <topics-testing-test_runner>`.
  34. Syndication feeds
  35. -----------------
  36. The :class:`django.contrib.syndication.feeds.Feed` class is being
  37. replaced by the :class:`django.contrib.syndication.views.Feed` class.
  38. The old ``feeds.Feed`` class is deprecated. The new class has an
  39. almost identical API, but allows instances to be used as views.
  40. Also, in accordance with `RSS best practices`_, RSS feeds will now
  41. include an ``atom:link`` element. You may need to update your tests to
  42. take this into account.
  43. For more information, see the full :doc:`syndication framework
  44. documentation </ref/contrib/syndication>`.
  45. .. _RSS best practices: http://www.rssboard.org/rss-profile
  46. Cookie encoding
  47. ---------------
  48. Due to cookie-handling bugs in Internet Explorer, Safari, and possibly
  49. other browsers, Django's encoding of cookie values was changed so that
  50. the characters comma (',') and semi-colon (';') are treated as
  51. non-safe characters, and are therefore encoded as ``\054`` and
  52. ``\073`` respectively. This could produce backwards incompatibilities
  53. if you are relying on the ability to set these characters directly in
  54. cookie values.
  55. What's new in 1.2 beta
  56. ======================
  57. This 1.2 beta release marks the final feature freeze for Django 1.2;
  58. while most feature development was completed for 1.2 alpha (which
  59. constituted a freeze on major features), a few other new features were
  60. added afterward and so are new as of 1.2 beta.
  61. Object-level permissions
  62. ------------------------
  63. A foundation for specifying permissions at the per-object level was
  64. added in Django 1.2 alpha but not documented with the alpha release.
  65. The default authentication backends shipped with Django do not
  66. currently make use of this, but third-party authentication backends
  67. are free to do so. See the :doc:`authentication docs </topics/auth>`
  68. for more information.
  69. Permissions for anonymous users
  70. -------------------------------
  71. If you provide a custom authentication backend with the attribute
  72. ``supports_anonymous_user`` set to ``True``, the ``AnonymousUser``
  73. class will check the backend for permissions, just as the normal
  74. ``User`` does. This is intended to help centralize permission
  75. handling; apps can always delegate the question of whether something
  76. is allowed or not to the authorization/authentication system. See the
  77. :doc:`authentication docs </topics/auth>` for more details.
  78. ``select_related()`` improvements
  79. ---------------------------------
  80. The ``select_related()`` method of ``QuerySet`` now accepts the
  81. ``related_name`` of a reverse one-to-one relation in the list of
  82. fields to select. One-to-one relations will not, however, be traversed
  83. by a depth-based ``select_related()`` call.
  84. The Django 1.2 roadmap
  85. ======================
  86. Before the final Django 1.2 release, at least one additional
  87. preview/development releases will be made available. The current
  88. schedule consists of at least the following:
  89. * Week of **March 2, 2010**: First Django 1.2 release
  90. candidate. String freeze for translations.
  91. * Week of **March 9, 2010**: Django 1.2 final release.
  92. If necessary, additional beta or release-candidate packages will be
  93. issued prior to the final 1.2 release. Django 1.2 will be released
  94. approximately one week after the final release candidate.
  95. What you can do to help
  96. =======================
  97. In order to provide a high-quality 1.2 release, we need your
  98. help. Although this beta release is, again, *not* intended for
  99. production use, you can help the Django team by trying out the beta
  100. codebase in a safe test environment and reporting any bugs or issues
  101. you encounter. The Django ticket tracker is the central place to
  102. search for open issues:
  103. * http://code.djangoproject.com/timeline
  104. Please open new tickets if no existing ticket corresponds to a problem
  105. you're running into.
  106. Additionally, discussion of Django development, including progress
  107. toward the 1.2 release, takes place daily on the django-developers
  108. mailing list:
  109. * http://groups.google.com/group/django-developers
  110. ... and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If you're
  111. interested in helping out with Django's development, feel free to join the
  112. discussions there.
  113. Django's online documentation also includes pointers on how to
  114. contribute to Django:
  115. * :doc:`How to contribute to Django </internals/contributing>`
  116. Contributions on any level -- developing code, writing documentation
  117. or simply triaging tickets and helping to test proposed bugfixes --
  118. are always welcome and appreciated.
  119. Development sprints for Django 1.2 will also be taking place at PyCon
  120. US 2010, on the dedicated sprint days (February 22 through 25), and
  121. anyone who wants to help out is welcome to join in, either in person
  122. at PyCon or virtually in the IRC channel or on the mailing list.