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 neologix
Recipients kushal.das, nedbat, neologix
Date 2013-05-06.11:52:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> I am interested to submit a patch on this. Should I move the implementation to os module and made the multiprocessing one as an alias ? or keep it in both places ?

Yes, you should move it, add a corresponding documentation to
Doc/modules/os.rst (you can probably reuse the multiprocessing doc),
and add a test in Lib/test/ (you can also probably reuse the
multiprocessing test).

> I prefer the idea of returning -1 instead of the current way of raising NotImplementedError in case we can not determine the number of CPU(s).

Seriously, I don't see what this brings. Since the user can't do
anything except using 1 instead, why not do this in the library?
I've searched a bit, and other platforms (.e.g Java, Ruby) don't raise
an exception, and always return a positive value.
Date User Action Args
2013-05-06 11:52:15neologixsetrecipients: + neologix, nedbat, kushal.das
2013-05-06 11:52:15neologixlinkissue17914 messages
2013-05-06 11:52:15neologixcreate