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 trent
Recipients jszakmeister, ned.deily, ronaldoussoren, sbt, trent, vstinner
Date 2013-03-19.18:50:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On Tue, Mar 19, 2013 at 01:58:59AM -0700, John Szakmeister wrote:
> John Szakmeister added the comment:
> Actually, Trent's version looks at hw.logicalcpu and then falls back
> to hw.ncpu, if there was an error.  Given the state of the
> documentation on these parameters, it's hard to say whether it's right
> or wrong, but at least hw.logicalcpu scales correctly if I disable
> some of the processors.

    That's pretty much the rationale I used.  I tested the fallback on
    OS X manually (i.e. the _bsd_cpu_count()), and that works, and the
    hw.logicalcpu definitely works in the first place, so, I figured it
    was good enough.

    I'll raise a new issue for os.cpu_count().
Date User Action Args
2013-03-19 18:50:02trentsetrecipients: + trent, ronaldoussoren, vstinner, jszakmeister, ned.deily, sbt
2013-03-19 18:50:02trentlinkissue17444 messages
2013-03-19 18:50:02trentcreate