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 pablogsal
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-14.13:16:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526303807.18.0.682650639539.issue20104@psf.upfronthosting.co.za>
In-reply-to
Content
I think that is the biggest argument towards using a tuple: that just setting the priority is not enough (and also is decontextualized as different policies have different priorities). On the other hand one could say that the API is a low level API and therefore the user should be aware of such a problem. Also, using a tuple makes the API a bit asymmetric as Serhiy mention but I think this can compensate for the conceptual map the will be established (as in each priority is associated with a policy) if the tuple API is used.
History
Date User Action Args
2018-05-14 13:16:47pablogsalsetrecipients: + pablogsal, gregory.p.smith, vstinner, benjamin.peterson, ned.deily, alex, dhduvall, neologix, gennad, martin.panter, serhiy.storchaka, John Jones, miss-islington
2018-05-14 13:16:47pablogsalsetmessageid: <1526303807.18.0.682650639539.issue20104@psf.upfronthosting.co.za>
2018-05-14 13:16:47pablogsallinkissue20104 messages
2018-05-14 13:16:47pablogsalcreate