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 Marc.Abramowitz
Recipients Marc.Abramowitz
Date 2012-05-20.03:56:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337486212.38.0.32150232851.issue14861@psf.upfronthosting.co.za>
In-reply-to
Content
Currently, the devguide (http://docs.python.org/devguide/) mentions two sets of commands for running the CPython test suite:

* For Python 3, one uses: ./python -m test

* For Python 2.7, one must use: ./python -m test.regrtest because ./python -m test fails with an error:No module named test.__main__; 'test' is a package and cannot be directly executed

If you take these two variations and multiply by the 3 variations of "python" command required depending on the OS (Windows, OS X, or other), then there are 6 permutations. I would say that this doesn't exactly encourage newcomers to CPython to contribute.

To take away a bit of the complexity, I have an extremely simple patch that adds one two line file to make ./python -m test work on 2.7.
History
Date User Action Args
2012-05-20 03:56:52Marc.Abramowitzsetrecipients: + Marc.Abramowitz
2012-05-20 03:56:52Marc.Abramowitzsetmessageid: <1337486212.38.0.32150232851.issue14861@psf.upfronthosting.co.za>
2012-05-20 03:56:51Marc.Abramowitzlinkissue14861 messages
2012-05-20 03:56:51Marc.Abramowitzcreate