[issue12747] Move devguide into /Docs of cpython repo

Ezio Melotti added the comment: Actually if we move the devguide to Doc/ we will have to maintain a copy for each branch -- that's the real reason why it's in a separate repo. So I think it's better to leave the devguide in a separate repo, and keep using it to document things that are not st

[issue12747] Move devguide into /Docs of cpython repo

Ezio Melotti added the comment: I'm +0 about it. See also #12409. -- components: +Devguide nosy: +ezio.melotti, sandro.tosi ___ Python tracker ___ _

[issue12747] Move devguide into /Docs of cpython repo

New submission from Eric Snow : The idea of moving the devguide into the cpython repo, presumably under Doc/, was mentioned in a thread on python-dev[1] (related to issue 12652). Does anyone have any objections? I'm guessing that Brett made a separate repo (A) for simplicity and (B) because