homepage

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 serhiy.storchaka
Recipients John Jones, alex, benjamin.peterson, dhduvall, gennad, gregory.p.smith, martin.panter, miss-islington, ned.deily, neologix, pablogsal, serhiy.storchaka, vstinner
Date 2018年05月07日.12:56:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525697812.92.0.682650639539.issue20104@psf.upfronthosting.co.za>
In-reply-to
Content
I have doubts about combining setschedpolicy and setschedparam.
On one hand, they are set by independent functions in C and have separate flags. When pass arguments separately we don't need to invent a parameter name: just remove the common "posix_spawnattr_" prefix from corresponding C function names. Passing scheduler=(None, param) looks clumsy. And from implementation side, parsing separate arguments is easier that parsing a single argument as a 2-tuple.
On other hand, these arguments are not completely independent: the setschedparam argument is required if setschedpolicy is specified.
Passing as separate arguments still looks more preferable to me.
History
Date User Action Args
2018年05月07日 12:56:53serhiy.storchakasetrecipients: + serhiy.storchaka, gregory.p.smith, vstinner, benjamin.peterson, ned.deily, alex, dhduvall, neologix, gennad, martin.panter, John Jones, pablogsal, miss-islington
2018年05月07日 12:56:52serhiy.storchakasetmessageid: <1525697812.92.0.682650639539.issue20104@psf.upfronthosting.co.za>
2018年05月07日 12:56:52serhiy.storchakalinkissue20104 messages
2018年05月07日 12:56:52serhiy.storchakacreate

AltStyle によって変換されたページ (->オリジナル) /