And DEP20 for Django philosophy :}
https://docs.djangoproject.com/en/dev/misc/design-philosophies/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-d
On 15 avr. 2014, at 08:41, Russell Keith-Magee wrote:
> ... and we should probably reserve DEP8 for our coding style guide :-)
... which brings the question of the relation between DEPs and online docs.
We already have a coding style guide in the docs.
I assume it's fine if DEP8 is just a link
On Tue, Apr 15, 2014 at 2:32 PM, Aymeric Augustin
wrote:
> On 15 avr. 2014, at 02:41, Russell Keith-Magee
> wrote:
>
>> On Tue, Apr 15, 2014 at 2:17 AM, Aymeric Augustin
>> wrote:
>>> \Would it be interesting to retro-spec the major features added in the past?
>>
>> I agree - there are a bunch
On 15 avr. 2014, at 02:41, Russell Keith-Magee wrote:
> On Tue, Apr 15, 2014 at 2:17 AM, Aymeric Augustin
> wrote:
>> \Would it be interesting to retro-spec the major features added in the past?
>
> I agree - there are a bunch of wiki pages that capture a lot of this
> information; it wouldn't
ot to introduce too much inertia.
We also talked about doing it immediately, just using pull requests on
GitHub, to get some momentum going. No need to build any fancy systems, etc.
Today at the sprints, I went ahead and started drafting how this would
work. Here is a new GitHub repo for DEPs (Dja
I'll be the first one to bite and submit
one https://github.com/django/deps/pull/1 It needs a lot of work as noted
in the PR but I'm happy to be a guinea pig for the process.
Best,
Mark
On Monday, April 14, 2014 8:41:07 PM UTC-4, Russell Keith-Magee wrote:
>
> On Tue, Apr 15, 2014 at 2:17 AM,
On Tue, Apr 15, 2014 at 2:17 AM, Aymeric Augustin
wrote:
> On 14 avr. 2014, at 19:51, Adrian Holovaty wrote:
>
>> One idea was to start doing a Django equivalent of Python's PEPs, which
>> would serve as a formal way to document large new features/changes in Django.
>
> Would it be interesting t
+1
On Mon, Apr 14, 2014 at 3:39 PM, Alex Gaynor wrote:
> The same way we do now?
>
>
> On Mon, Apr 14, 2014 at 3:34 PM, Andrew Farrell wrote:
>
>> Who is responsible then for deciding what the conclusion of the
>> discussion was? If there is no such person, how does the process handle the
>> ca
The same way we do now?
On Mon, Apr 14, 2014 at 3:34 PM, Andrew Farrell wrote:
> Who is responsible then for deciding what the conclusion of the discussion
> was? If there is no such person, how does the process handle the case when
> people talk past each other and don't actually come to a conc
Who is responsible then for deciding what the conclusion of the discussion
was? If there is no such person, how does the process handle the case when
people talk past each other and don't actually come to a conclusion?
On Mon, Apr 14, 2014 at 2:22 PM, Michael Manfre wrote:
> I think there would
I think there would be value in adding DEPs for the major features that
will ship with 1.7.
Regards,
Michael Manfre
On Mon, Apr 14, 2014 at 2:17 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> On 14 avr. 2014, at 19:51, Adrian Holovaty wrote:
>
> > One idea was to start d
On 14 avr. 2014, at 19:51, Adrian Holovaty wrote:
> One idea was to start doing a Django equivalent of Python's PEPs, which would
> serve as a formal way to document large new features/changes in Django.
Would it be interesting to retro-spec the major features added in the past?
--
Aymeric.
ny fancy systems, etc.
>
> Today at the sprints, I went ahead and started drafting how this would
> work. Here is a new GitHub repo for DEPs (Django Enhancement Proposals):
>
> https://github.com/django/deps
>
> And here is DEP 1, a draft attempt to document how the process
ad and started drafting how this would work.
> Here is a new GitHub repo for DEPs (Django Enhancement Proposals):
>
> https://github.com/django/deps
>
> And here is DEP 1, a draft attempt to document how the process works:
>
> https://github.com/django/deps/blob/master/deps
ked about doing it immediately, just using pull requests on
GitHub, to get some momentum going. No need to build any fancy systems, etc.
Today at the sprints, I went ahead and started drafting how this would
work. Here is a new GitHub repo for DEPs (Django Enhancement Proposals):
https://github.
On 12/1/07, Simon Willison <[EMAIL PROTECTED]> 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 aggrega
On Dec 1, 2:02 am, Simon Willison <[EMAIL PROTECTED]> 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/d
+1 from me, this also a document that developers can look at and plan around
very succinctly.
On Dec 1, 2007 3:02 PM, Simon Willison <[EMAIL PROTECTED]> 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. At the mo
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
19 matches
Mail list logo
