Proposed features for Django 1.1

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

ORM:

• ​ORM aggregation (see also ​this django-dev thread)
• ​Object history (discussed many times in django-dev as well)
• 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
• Support for 'DISTINCT ON' queries with QuerySet.distinct()
• ​Support denormalization (#8946, see also ​Cal Henderson's DjangoCon talk)
• Allow database API users to specify the fields to exclude in a SELECT statement
• ​Day of Week filter on Date/DateTime Fields (see ticket #7672)
• ​Native autocommit option for Postgresql backend (see ticket #3460)
• Provide the ability to update database to reflect changes in model definitions (i.e., schema evolution) (see also Database Migrations and SchemaEvolution)
• Add signals to ManyRelatedManager ​Access to m2m relations in model.save

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
• ​django.forms.SafeForm - forms with built-in CSRF protection
• Refactor django.template (see also: ​these ​django-dev ​threads)
• Add an append method to ErrorDict
• Add a session based form wizard (see also ​this django-dev thread)
• Remove blank spaces with strip when validating data

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
• ModelAdmin should allow for overriding of ForeignKey/ManyToMany options
• Add the ability to add fields to admin forms and the ability to intercept form submissions so the values of those fields could be accessed. This way admin plugins could be developed.

Serving dynamic content:

• ​`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)
• ​Add support for streamed content (see also #7581)

Files:

• Fix missing proxies throughout django.core.files.* -- See: tickets #9344 and #9404, and also ​on the dev-list.

Comments:

• ​customizability of contrib.comments (see also #8630)
• Inclusion of comment-utils

Testing, debugging:

• Follow redirect chains on the Test Client
• Disable all e-mail sending for debugging
• Make the Django testcases use transactions to rollback DB changes created in a test
• ​Create a benchmark to measure the impact changes have to code (ticket #8949)
• ​Integrate the recording of tests into the Django testserver command

General:

• Please make Django installable with easy_install (ticket #6972, #3812)
• the four features that were deferred until post-1.0
• Class-Based Generic Views
• ​URL resolver refactor
• ​Integrate GSOC2008 search project
• ​Avoid double imports (see 8193)
• Message Passing For Anonymous Users
• Honour the REMOTE_USER provided by the server
• Implement Atom Publishing Protocol (and related #3569)
• ​Signal Connection Decorators (see #9015)
• ​Some form of media management for apps
• ​Address logging
• ​A preferred way of creating breadcrumbs would be nice. This would improve plugability of applications
• Multilingual support in the db. There are some projects that could be integrated into the trunk as django-multilingual.
• ​Decoupling authentication from calling a view
• (?) ​Signed cookies (#3285 seems to be closed as wontfix, but as the feature is genrally useful, it may be justified to be a contrib app; see also ​http://code.google.com/p/django-signedcookies)
• ​AnonymousUser that you can set specific permissions for
• ​Allow for extendable auth_user module (add an abstract base class for User too)

---

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;