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-21.15:39:56
SpamBayes Score 0.000355127
Marked as misclassified No
Message-id <1319211597.39.0.736570107019.issue13228@psf.upfronthosting.co.za>
In-reply-to
Content
> +   ``hg clone http://hg.python.org/cpython``;
> I use http://hg.python.org/cpython#default to avoid cloning the 2.x 
> branches, that’s an optimization that can save some time and space.

I think in the default case it's easier to get'em all.

> +2. run ``./configure --with-pydebug && make -j2``
> Is make -j2 harmless on single-CPU systems?  Doesn’t our make default 
> to -j0 anyway, to use all CPUs?

As far as I know, -j2 is harmless on single-CPU systems, but I don't think we use all the CPUs by default with a plain `make`.

> +3. :doc:`run the tests <runtests>` with ``./python -m test``;
> Is that cross-platform?  Mac OS X has python.exe for example.

These instructions are a bit UNIX/Linux-centric, because that's what most developers seems to use.  On Mac OS it would indeed be ./python.exe, but it shouldn't take long for the developers to figure that out or click on the link and see how it works for their OS.

If you think it's worth to expand a bit, I guess we could still do it.
History
Date User Action Args
2011-10-21 15:39:57ezio.melottisetrecipients: + ezio.melotti, terry.reedy, eric.araujo
2011-10-21 15:39:57ezio.melottisetmessageid: <1319211597.39.0.736570107019.issue13228@psf.upfronthosting.co.za>
2011-10-21 15:39:56ezio.melottilinkissue13228 messages
2011-10-21 15:39:56ezio.melotticreate