Hi,
Responding to Trygve and Kenney from here (beaver suffered an outtage).
Just looking at the PEPs (http://www.python.org/dev/peps/) and looks like a
good idea. They have templates and my argument for the same format is the
historical success of couching problems a la The Pattern Language as i
On 5/15/06, Jesse McConnell <[EMAIL PROTECTED]> wrote:
I think this is a great idea, it would be a good exercise to go
through the existing ideas that are slated and clean them up in a
clear well reasoned way. the limited amount in the queue at any one
point in time is probably a good idea as w
I think this is a great idea, it would be a good exercise to go
through the existing ideas that are slated and clean them up in a
clear well reasoned way. the limited amount in the queue at any one
point in time is probably a good idea as well...force the asking of
the tough questions and whatnot
Jason van Zyl wrote:
Hi,
I was just looking at the wiki for the 2.1 design stuff and was
wondering if we could use a common format for each issue? I was
thinking that we may borrow from a Pattern Language and for each issue
have a Context, Problem, Solution, and maybe Implementation Detai
On Sun, 14 May 2006, Jason van Zyl wrote:
[snip]
> I think this would make it easier for each person to grok if we had a
> common pattern. And common patterns is what we're about.
True, although you have to read the entire issue to completely understand
it, so for me personally it doesn't matt
Hi,
I was just looking at the wiki for the 2.1 design stuff and was
wondering if we could use a common format for each issue? I was
thinking that we may borrow from a Pattern Language and for each
issue have a Context, Problem, Solution, and maybe Implementation
Details. So for something
