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 pitrou
Recipients eric.araujo, ezio.melotti, pitrou, terry.reedy
Date 2011-10-21.16:26:30
SpamBayes Score 1.3107862e-06
Marked as misclassified No
Message-id <1319214150.3382.3.camel@localhost.localdomain>
In-reply-to <1319214145.17.0.0489756908708.issue13228@psf.upfronthosting.co.za>
Content
> New patch that adds a few more instructions for Windows/Mac OS.  `make
> test` is UNIX-specific, so I left `./python -m test`.
> I also moved the section before the quick links, since it seems to me
> more interesting that those links (you don't usually want to start
> from the PEPs or the buildbot page).

You want at the minimum "python -m test -j3", I think (many tests don't
really use the CPU).
Your Windows instructions could be improved a bit:
- not "the project files from the PCbuild" directory, but
"PCbuild/pcbuild.sln" (there are many project files)
- not "python.exe", but "PCbuild\python_d.exe"
History
Date User Action Args
2011-10-21 16:26:31pitrousetrecipients: + pitrou, terry.reedy, ezio.melotti, eric.araujo
2011-10-21 16:26:31pitroulinkissue13228 messages
2011-10-21 16:26:30pitroucreate