Context Navigation

Django 1.2 features

These are the features proposed for inclusion in Django 1.2, broken into high, medium, and low priorities. For more
details, see Version1.2Roadmap.

Each feature lists which committer(s) are involved, and who's the primary implementor (aka lieutenant aka "LT"). This is
a wiki, so if you're the primary on a feature below and don't see yourself, please fix it.

Note: Contrib-09 and ORM-07 are controversial (both +1 and -1 votes) and may need discussion on django-dev before commit.

Highly unlikely

Some features were voted on and were essentially rejected from 1.2. They're labeled "highly unlikely" to reflect that
fact that consensus can change. However, with multiple -1 votes, the following features are highly unlikely to make
it into Django 1.2:

Admin-03 (Support for input arguments on admin actions.) - this would overly complicate the admin UI and dilute the purpose of the admin actions.

Contrib-01 (Add South to contrib) - general consensus - including that of South's lead developer - is that South isn't yet ready to be a bonafide part of Django.

Not in consideration

Small, or Just Bugs

Features proposed on this list that area just bugs to be fixed or really tiny feature additions that are not controversial in any way. They're still here for posterity, but have no real role in the feature proposal process.

Rejected procedurally

These are proposed features that, as of the close date for proposals, lacked concrete proposals, proof-of-concept implementations, or details needed to start implementing.

Add a generic "official" way to create a REST API; so far there are quite a bunch of pluggables, with varying levels of "completeness", documentation and efficiency, and they're quite hard to choose from.

Make easier to mantain / deploy default settings.py by either:

include localsettings at the end, with the recommended approach of putting DATABASE_* settings in localsettings.py