Part of it is that the official docs often aren't all that precise compared to the PEP. Part of it is that the PEP is still marked provisional, and we wish to declare it final as of 3.6.0 (or as of 3.6b1, depending on who you talk to). So I'd like to see the "final" version correspond with the API as of that point.
But I agree it's not super important. On Mon, Sep 12, 2016 at 3:05 PM, Ned Batchelder <n...@nedbatchelder.com> wrote: > I'm curious why it's important to update the PEP? I would think the docs > should be the official source of truth about the library, and the PEP > should be a record of the decisions that lead to the library. Trying to > keep both in sync just seems like extra work. Why not put a notice at > the top of the PEP indicating that it was accurate when it was accepted, > but that changed have happened since then, see the docs for details? > > --Ned. > > > On 9/11/16 9:53 PM, Yury Selivanov wrote: >> Guido and I are looking for help with PEP 3156. Currently it's out of >> sync with the docs. It would be cool if someone could volunteer and >> update it (at least make sure that all APIs are up to date). >> >> Yury >> _______________________________________________ >> Python-ideas mailing list >> Python-ideas@python.org >> https://mail.python.org/mailman/listinfo/python-ideas >> Code of Conduct: http://python.org/psf/codeofconduct/ > > _______________________________________________ > Python-ideas mailing list > Python-ideas@python.org > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/ -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
