[issue12747] Move devguide into cpython repo

Eric Snow added the comment: That's fine. The discussion had moved away from the devguide, so I figured it would be worth following up. You guys have made some good points. -- resolution: -> rejected status: open -> closed ___ Python tracker

[issue12747] Move devguide into cpython repo

Nick Coghlan added the comment: I'd say the main reason the dev guide is in a separate repo is the historical one (i.e. Brett was working on it as a separate repo prior to the hg migration and we never merged it). However, the version independent nature of the material is the main argument a

[issue12747] Move devguide into cpython repo

Ezio Melotti added the comment: The possible options I see are: 1) move it in Doc/ or some other dir -- but we will have to maintain it in all the branches; 2) keep it only in the default branch -- but we will have to remove it from the old branch when we cut a release; 3) make a

[issue12747] Move devguide into cpython repo

Eric Snow added the comment: I suppose it doesn't have to be in Doc/. -- title: Move devguide into /Docs of cpython repo -> Move devguide into cpython repo ___ Python tracker _