Suggestion: DEPs - Django Enhancement Proposals

63 views
Skip to first unread message

Simon Willison

unread,
Nov 30, 2007, 9:02:00 PM11/30/07
to Django developers
Here's an idea that's been kicking around in the back of my head for
far too long: Django Enhancement Proposals, or DEPs. At the moment,
large changes to Django (auto escaping, queryset refactor etc) are
discussed in quite an ad-hoc way - if you want to stay completely up
to date on them you need to be following mailing lists, tracking
branches and talking directly to the developers. It would be great if
these changes had a slightly more formal structure, and in particular
a single document that described the design decision and what was
going on.

We're already doing this on the wiki for most things so it wouldn't be
an enormous change, but formalising it a bit could help make things
clearer. Python's PEPs work brilliantly; could the same idea work for
Django as well?

Mike Scott

unread,
Nov 30, 2007, 9:10:00 PM11/30/07
to django-d...@googlegroups.com
+1 from me, this also a document that developers can look at and plan around very succinctly.

Simon Willison

unread,
Nov 30, 2007, 10:10:56 PM11/30/07
to Django developers
On Dec 1, 2:02 am, Simon Willison <si...@simonwillison.net> wrote:
> Here's an idea that's been kicking around in the back of my head for
> far too long: Django Enhancement Proposals, or DEPs.

For further context it's worth reading PEP 1, which describes PEPs and
how they work:

http://www.python.org/dev/peps/pep-0001/

I don't think DEPs would need to be quite as strictly structured
(there's a fair amount of administrative overhead involved in PEPs),
but we could certainly adapt a slightly more lightweight version of
the PEP system.

Russell Keith-Magee

unread,
Dec 3, 2007, 7:08:23 AM12/3/07
to django-d...@googlegroups.com
On 12/1/07, Simon Willison <si...@simonwillison.net> wrote:
>
> Here's an idea that's been kicking around in the back of my head for
> far too long: Django Enhancement Proposals, or DEPs.

+1 There are any number of big features - m2m intermediate tables (now
ticket #6095), model inheritance and aggregate clauses to pick some
big examples - that have been well discussed, but not implemented.
Collating the knowledge from a multitude of disparate posts into a
formal DEP document sounds like a good idea to me.

Yours,
Russ Magee %-)

Reply all
Reply to author
Forward
0 new messages