| 90 | The following features were reviewed highly and are generally accepted as |
| 91 | "wanted", but currently are lacking a "champion" to see the feature done. This |
| 92 | means these features are likely to be included in 1.1 if finished, but are |
| 93 | a sort of "second-tier": |
| 94 | |
| 95 | * [Contrib-01] Session-based form wizard. |
| 96 | * [Form-02] ``django.forms.SafeForm`` - forms with built-in CSRF protection. |
| 97 | * [ORM-09] ``Manager.update_or_create()`` and ``Model.update()``. |
| 98 | * [ORM-10] ``QuerySet.select_for_update()`` method. |
| 99 | * [ORM-11] ``QuerySet.cache()`` method. |
| 100 | * [ORM-12] Allow the use of ``property()`` in fields. |
| 101 | * [ORM-13] Support for ``DISTINCT ON`` queries with ``QuerySet.distinct()``. |
| 102 | * [ORM-16] Native autocommit option for Postgresql backend. |
| 103 | * [ORM-18] Add signals to many-to-many objects. |
| 104 | * [Template-01] Extend inclusion tag syntax to allow custom templates. |
| 105 | * [Template-04] Clean-up of ``django.template`` internals. |
| 106 | * [Template-05] Namespace support for template libraries. |
| 107 | |
| 108 | Special cases |
| 109 | ------------- |
| 110 | |
| 111 | As is to be expected, a few features don't fit so easily into any of the hard |
| 112 | categories: |
| 113 | |
| 114 | * [ORM-05] Sharing of ``selected_related()`` data in memory, and/or an |
| 115 | ORM identity map. |
| 116 | |
| 117 | The scope of this feature is a bit nebulous, but it's under discussion |
| 118 | on `django-developers`_. If consensus is reached and the feature can |
| 119 | be implemented in time, it'll get into 1.1. |
| 120 | |
| 121 | * [Form-01] Selectable HTML output for forms/fields. |
| 122 | |
| 123 | This feature is similarly not fully-scoped, though this one has a |
| 124 | reference implementation so it's further along. However,, there's a fair |
| 125 | bit of controversy about the particular proposed implementation. Again, |
| 126 | consensus is the issue here; discussion is ongoing. |
| 127 | |
| 128 | * [View-02] Add ``RequestContext`` by default in ``render_to_response``. |
| 129 | |
| 130 | This proposal is strongly controversial, with multiple +1 and -1 votes. |
| 131 | As such, consensus seems unlikely; a middle-ground approach will need be |
| 132 | found, which likely pushes this out of scope for 1.1. |
| 133 | |