Proposed features for Django 1.1

Please list any proposed features for 1.1 below, along with links to relevent tickets, django-dev discussions, etc.

ORM:

• ​ORM aggregation (see also ​this django-dev thread)
• model validation
• ​Manager.update_or_create (see also #3182)
• add optional FOR UPDATE clause to QuerySets
• ​multiple database APIs
• Cache queryset results
• Identity Map (see also DjangoSpecifications/Core/SingleInstance)
• Referencing fields in queries and updates in the ORM (possibly part of django aggregation, I know the GSOC student has worked on this)
• Make select_related work with reverse onetoones
• Allow the use of property() in fields

Forms and templates:

• ​better HTML output for form fields (see also ​django-html)
• Extend inclusion tag syntax to allow custom templates
• Enhanced simple-tag decorator (access to context and easy block tags) (see also ​django-dev thread)
• Add keyword support to simple_tag and inclusion_tag

Admin:

• ​Multiple edit arbitrary fields in the admin
• ​Integrate Databrowse into the admin
• ​Integration of django-batchadmin into core
• Switch the admin to use a url resolver and be reversable
• Improve flexibility of admin.autodiscover for custom admin sites

General:

• the four features that were deferred until post-1.0
• ​customizability of contrib.comments (see also #8630)
• Class-Based Generic Views
• ​URL resolver refactor
• ​Object history (discussed many times in django-dev as well)
• ​Integrate GSOC2008 search project
• ​Avoid double imports (see 8193)
• Message Passing For Anonymous Users
• Follow redirect chains on the Test Client
• Honour the REMOTE_USER provided by the server
• Disable all e-mail sending for debugging
• ​`wsgi.file_wrapper` for large file serving (see also #2131, #7894 and ​http://www.python.org/dev/peps/pep-0333/#optional-platform-specific-file-handling)
• Make the Django testcases use transactions to rollback DB changes created in a test
• Implement Atom Publishing Protocol

---

Misc:

• create a list of tickets in trac db that have a high interested people count (as if something is important to many, it should be considered):

  select summary from ticket where length(cc) > 50;