headers
Jim Jewett | 10 Oct 17:51

syntax change justification

Nick Coghlan's explanation of what justifies a syntax change (most of message
http://mail.python.org/pipermail/python-dev/2008-October/082831.html )
should probably be added to the standard docs/FAQs somewhere.

At the moment, I'm not sure exactly where, though.  At the moment, the
Developer FAQ (http://www.python.org/dev/faq/)  is mostly about using
specific tools (rather than design philosophy), and Nick's explanation
may be too detailed for the current Explanations section of
www.python.org/dev/

Possibly as a Meta-PEP?

-jJ
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |
headers
Brett Cannon | 10 Oct 19:31
Favicon

Re: syntax change justification

On Fri, Oct 10, 2008 at 8:51 AM, Jim Jewett <jimjjewett <at> gmail.com> wrote:
> Nick Coghlan's explanation of what justifies a syntax change (most of message
> http://mail.python.org/pipermail/python-dev/2008-October/082831.html )
> should probably be added to the standard docs/FAQs somewhere.
>
> At the moment, I'm not sure exactly where, though.  At the moment, the
> Developer FAQ (http://www.python.org/dev/faq/)  is mostly about using
> specific tools (rather than design philosophy), and Nick's explanation
> may be too detailed for the current Explanations section of
> www.python.org/dev/
>
> Possibly as a Meta-PEP?
>

What we need (and hope through some miracle to have the time for) a
doc that explains the steps needed to report a bug/submit a patch
(basically the issue lifecycle) and how to propose a new language
feature. That would clean up the dev FAQ into basically being a svn
FAQ, and then give us docs to point people to when they ask how they
can contribute.

-Brett
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |
headers
Terry Reedy | 10 Oct 22:53

Re: syntax change justification

Jim Jewett wrote:
> Nick Coghlan's explanation of what justifies a syntax change (most of message
> http://mail.python.org/pipermail/python-dev/2008-October/082831.html )
> should probably be added to the standard docs/FAQs somewhere.

I agree that this was a helpful explanation.  A link to the original 
would be easy to add now.

_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |
headers
Nick Coghlan | 11 Oct 03:05

Re: syntax change justification

Terry Reedy wrote:
> Jim Jewett wrote:
>> Nick Coghlan's explanation of what justifies a syntax change (most of
>> message
>> http://mail.python.org/pipermail/python-dev/2008-October/082831.html )
>> should probably be added to the standard docs/FAQs somewhere.
> 
> I agree that this was a helpful explanation.  A link to the original
> would be easy to add now.

A link from either the dev FAQ (like the one to Raymond's School of Hard
Knocks) or from PEP 1 (PEP Purpose and Guidelines) might work, but I
will leave it to others to decide whether it is worth linking to or not :)

Cheers,
Nick.

--

-- 
Nick Coghlan   |   ncoghlan <at> gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
            http://www.boredomandlaziness.org
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |

Gmane