Legend:

This page lists features which have been proposed for development/inclusion in Django 1.2. So far no decisions have been made regarding any of these features. See [wiki:Version1.2Roadmap] for information on the process and definition of terms.

6

6

7

== Features under consideration ==

8

* Multi-database support (Alex Gaynor's GSoC project)

7

== Major features ==

8

9

These are the feature proposals that represent major architectural changes for Django.

* Replace get_absolute_url() with methods that are more useful and have more realistic names (See also: ReplacingGetAbsoluteUrl)

82

* #8896 Support for subdomains in the url patterns, to allow easy reversing (or better: to allow reversing at all ;))

83

84

=== Views ===

85

* #8274 Auth views allow form override (as an example, this would allow usernames longer than 30 chars to be handled)

86

87

== Not in consideration ==

88

89

=== Small, or Just Bugs ===

90

91

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.

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.

105

21

106

* 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.

22

107

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

23

108

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

* Make working with inline formsets easier (http://stackoverflow.com/questions/442040/pre-populate-an-inline-formset, as per James: ''...the way the model formsets work just make this more trouble than it's usually worth, but with a bit of API cleanup I think it could be made extremely easy.'', also http://groups.google.com/group/django-developers/browse_thread/thread/f9aae709a7fda689)

30

114

* Allow inclusion of inlines in fieldsets (admin)

31

* Add South (http://south.aeracode.org/) or some other migration/evolution app to contrib (http://code.djangoproject.com/wiki/SchemaEvolution)