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 tzickel
Recipients crwilcox, giampaolo.rodola, paul.moore, pitrou, robbuckley, steve.dower, tim.golden, tzickel, vstinner, zach.ware
Date 2017-09-01.19:52:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
One should be careful with this modification because of the Windows definition of process groups.

For example, if multi-threaded code thinks that by reading the value of the new os.cpu_count() it can use all the cores returned, by default it cannot as in windows processes by default can run only in a single process group (how it worked before).

We can see such code builtin python stdlib itself:

I think even .NET still uses the old way that python did until now:

Although some of this stuff is used in code for python multiprocess code which that might actually get a boost (since different process can get scheduled to different groups)
Date User Action Args
2017-09-01 19:52:24tzickelsetrecipients: + tzickel, paul.moore, pitrou, vstinner, giampaolo.rodola, tim.golden, zach.ware, steve.dower, crwilcox, robbuckley
2017-09-01 19:52:24tzickelsetmessageid: <>
2017-09-01 19:52:24tzickellinkissue30581 messages
2017-09-01 19:52:24tzickelcreate