This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients eric.araujo, ezio.melotti, terry.reedy
Date 2011-10-19.23:37:02
SpamBayes Score 5.0670407e-10
Marked as misclassified No
Message-id <1319067423.48.0.288389971536.issue13228@psf.upfronthosting.co.za>
In-reply-to
Content
Attached patch adds to the index page a list of 5 steps necessary to set up Python and make a patch.  These informations are currently scattered around a few pages and many contributors are already familiar with Mercurial and the process of creating patches, so they just need to know the address where to clone and the commands to compile Python and run the tests.
The list also includes links to the other sections, so users can find more detailed information if they need them (this is also valid for the second point: the "configure" command is specific to Unix, but the link has information about Windows too).
All this should make the devguide a bit more usable.

(A bit of background: during the sprints at PyCon FI I wrote the steps 1-3 on the whiteboard, and they worked well for everyone.  Most of them managed to get something done with no further assistance, even if a few people were not so familiar with Mercurial.)
History
Date User Action Args
2011-10-19 23:37:03ezio.melottisetrecipients: + ezio.melotti, terry.reedy, eric.araujo
2011-10-19 23:37:03ezio.melottisetmessageid: <1319067423.48.0.288389971536.issue13228@psf.upfronthosting.co.za>
2011-10-19 23:37:02ezio.melottilinkissue13228 messages
2011-10-19 23:37:02ezio.melotticreate