Brett Cannon added the comment: Here is the overall plan.
1. A README for core devs leading a sprint to make sure they remember to have the right repositories cloned, files downloaded, and docs built; stuff they already know how to do and thus don't need a tool to do for them which constantly breaks 2. Some helper scripts to make tricky or multi-step things an easy single step for both core devs and new contributors I finished step 1 on the plane home from PyCon and step 2 I'm in the process of doing. The full coverage script will be referenced from the devguide, but the steps themselves will not be outlined. Because it is constantly changing thanks to coverage.py moving at its own pace I don't want to update the script **and** the docs. So the devguide will point to the script and explain what it's for but not detail every step like it does now. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17465> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
