Version 1.0 Features
This page contains the list of features to be included in Django 1.0, and their status. See VersionOneRoadmap for more details on the process.
Unfinished Features
Must-have features
Feature | Lieutenant | Committer | Status | Tickets
|
newforms-admin | Brian Rosner, Karen Tracey | Joseph | in trunk; still bugs to kill | see report
|
oldforms -> newforms | Brian Rosner | JKM | in trunk; some cleanup still required | #3639, #7830 ...
|
"Maybe" features
Feature | Lieutenant | Committer | Status | Tickets
|
Signal performance improvements | Jeremy Dunck | JKM | needs feedback | #6814
|
INSTALLED_APPS refactoring | ??? | ??? | not started | #3591
|
File storage refactoring | Marty Alchin | JKM | awaiting final review | #5361
|
Model-level validation | Honza Král | JKM | started | #6845
|
GenericForeignKey support in nfa | ??? | Brian Rosner | not started | #4667
|
GeoDjango | Justin Bronn | Justin Bronn | nearly done, needs #7589, #7637; docs in progress | #7589, #7637, #7579, #6547, #7619
|
Fix alternative Python VM bugs | Maciej Fijalkowski(pypy), Leo Soto(jython) | JKM | ??? | #7560, #7441, #7303, #7339, #7727, #7728, #7751. Reopen #6857, unless #6814 will be commited.
|
De-cruftify template tag loading | Øyvind Saltvik | JKM | needs feedback | #6587, #3349, ...
|
Middleware ordering | ??? | JKM | needs feedback | #730
|
Finish documentation refactoring | ??? | JKM | needs work |
|
Comments refactor | Thejaswi Puthraya | ??? | in progress | #1829, #1853, #2134, #2177, #2228, #3091, #3546, #4189
|
Finished
Must-have features
Feature | Lieutenant | Committer | Ticket(s) | Commited in revision
|
WSGI compliance | Malcolm | Malcolm | #285 | [8015]
|
"Maybe" features
Feature | Lieutenant | Committer | Ticket(s) | Commited in revision
|
Large file uploads | Mike Axiak | JKM | #2070 | [7814]
|
Many-to-many intermediates | Eric Florenzano | Russ | #6095 | [8136]
|
Deferred Until Post-1.0
Feature | Lieutenant | Committer | Ticket
|
Self-referencing fields in queries | ??? | Russ | #7210
|
Alternative Python VMs
See VersionOneRoadmap for details.
Middleware ordering
We are not treating the middleware hierarchy as a stack, in the sense that if
one piece of middleware short-circuits the response construction, we go right to
the bottom of the pile before processing the request. We need to decide what
behaviour we really want here and record it. Both the referenced tickets have
good points in them and since this might slightly change request/response
behaviour, it's a pre-1.0 decision if possible.