On Wed, Aug 29, 2012 at 2:45 PM, Guido van Rossum wrote:
> Hm. I would be fine with the edits proposed, no need to bother others. But
> please do use the Hg repo. :-)
What? It's in Hg and I've been using Subversion all this time?
Oh, you had my hopes up for a while there. Alas, the problem is th
On Wed, Aug 29, 2012 at 2:45 PM, Guido van Rossum wrote:
> Hm. I would be fine with the edits proposed, no need to bother others. But
> please do use the Hg repo. :-)
Indeed :)
(Also, as described in PEP 1, any core committer can act as a PEP
editor - the p...@python.org address is most useful w
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
> >
> wrote:
> > Sending a patch to the PEP editors (p...@python.org ) or
> posting it to
>
On Wed, Aug 29, 2012 at 2:36 PM, Nick Coghlan wrote:
> Sending a patch to the PEP editors (p...@python.org) 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 implemente
On Wed, Aug 29, 2012 at 2:03 PM, Chris Angelico wrote:
> What's the procedure for making trivial edits to a PEP? I was
> (re)reading PEP 393 and found a couple of typos (PyCompactObject s/be
> PyCompactUnicodeObject and "differs form length" s/be "from"). Can I
> edit them directly in the web site
What's the procedure for making trivial edits to a PEP? I was
(re)reading PEP 393 and found a couple of typos (PyCompactObject s/be
PyCompactUnicodeObject and "differs form length" s/be "from"). Can I
edit them directly in the web site's SVN repo, or should a patch be
submitted?
Apologies for the
