= Specifications for various Django features =

'''NB: this page and it's sub-pages are in no way part of Django's official process.''' Feel free to use the wiki as a collaborative whiteboard for reaching agreement on designs of various issues, but please note that all discussion should happen on django-dev. Please read [http://www.djangoproject.com/documentation/contributing/#requesting-features requesting features] for more information on how Django's development process works.

Only use this page if the issue is non-trivial and spans many tickets or needs comprehensive elaboration that would be cumbersome to describe in a ticket.

== General ==

 * [wiki:DjangoSpecifications/Core/Threading Threading]

== Open proposals ==

Newforms-admin:
 * [wiki:DjangoSpecifications/NfAdmin/FlexibleAppHandling Usability improvements in application handling] (enhancements of the `app` directive)

Fields:
 * Binary field: merge information from #2417 and http://groups.google.com/group/django-developers/browse_thread/thread/266565a23b765ea2

Core:
 * [wiki:DjangoSpecifications/Core/SingleInstance Single Instance] aka the infamous #17

== Integrated proposals ==

 * [wiki:DjangoSpecifications/Contrib/Sessions Session framework improvements] integrated in [8340] - [8344]
 * [wiki:DjangoSpecifications/NfAdmin/MediaAndValidation Media and validation] integrated in [7360] and [7365]

== Obsolete/Rejected Proposals ==

 * [wiki:DjangoSpecifications/Docs/ConvertingRestToOtherFormats Converting the ReST documentation in `doc/` to HTML and PDF] -- will be superseded by a Sphinx-based solution.