➜

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 vstinner
Recipients amaury.forgeotdarc, anacrolix, benjamin.peterson, giampaolo.rodola, neologix, pitrou, python-dev, rosslagerwall, vstinner
Date 2012-08-04.00:31:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344040291.57.0.498667679316.issue12655@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm sorry, I missed this issue. I just saw its API and I have remarks on the cpu_set type:
 * Why not reusing the set type for input parameters and the result of sched_getaffinity?
 * Method names of cpu_set are very different than names of the set type
 * Why do I need to specify the number of CPU?

signal.pthread_sigmask() accepts any iterable object as input, convert it to a sigset_t. For the result, it converts the new sigset_t to a classic Python set object.

Is it possible to get the number of CPU to be able to convert a Python set to a cpu_set?
History
Date User Action Args
2012-08-04 00:31:32vstinnersetrecipients: + vstinner, amaury.forgeotdarc, pitrou, giampaolo.rodola, benjamin.peterson, anacrolix, neologix, rosslagerwall, python-dev
2012-08-04 00:31:31vstinnersetmessageid: <1344040291.57.0.498667679316.issue12655@psf.upfronthosting.co.za>
2012-08-04 00:31:30vstinnerlinkissue12655 messages
2012-08-04 00:31:29vstinnercreate