[Python-Dev] Copyediting PEPs (original) (raw)
Guido van Rossum guido at python.org
Wed Aug 29 06:45:04 CEST 2012
- Previous message: [Python-Dev] Copyediting PEPs
- Next message: [Python-Dev] Copyediting PEPs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hm. I would be fine with the edits proposed, no need to bother others. But please do use the Hg repo. :-)
On Tuesday, August 28, 2012, Chris Angelico wrote:
On Wed, Aug 29, 2012 at 2:36 PM, Nick Coghlan <ncoghlan at gmail.comjavascript:;> wrote: > Sending a patch to the PEP editors (peps at python.org javascript:;) or posting it to > the tracker is likely the best option. However, in the general case, > we don't worry too much about minor errors in accepted and final PEPs > - once the PEP is implemented, they're mostly historical records > rather than reference documents
Thanks. I'll not worry about it then; PEP 393 is final. ChrisA
Python-Dev mailing list Python-Dev at python.org javascript:; http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
-- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120828/64e99308/attachment.html>
- Previous message: [Python-Dev] Copyediting PEPs
- Next message: [Python-Dev] Copyediting PEPs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]