python / devinabox Goto Github PK

While it's nice to have, it hides a key aspect of the development cycle from people that they should probably learn about anyway. Plus it's very UNIX-specific and leaves WIndows users out in the cold.

To address this the build_python.py file should be deleted and the README updated.

It's still referencing Mercurial stuff :)

Nick and I both agreed that the devinabox should be under an Apache license with the copyright held by the PSF.

Once python/core-workflow#18 is dealt with, the instructions become superfluous. It would be better to point people at the Travis file on how to run coverage than keep a separate set of instructions.

Will get us nice formatting.

Following up from python/devguide#201

and
python/devguide#7

Also include instructions on how to install the prereqs.

http://bugs.python.org/issue21012

Update README.rst to be more user friendly for sprint leaders (who will likely be experienced developers but may not be a core developer).

Use spacing, word choice, and formatting to help make the README easier for the user to skim.