Message316503
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. |
|
Date |
User |
Action |
Args |
2018-05-14 13:16:47 | pablogsal | set | recipients:
+ 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:47 | pablogsal | set | messageid: <1526303807.18.0.682650639539.issue20104@psf.upfronthosting.co.za> |
2018-05-14 13:16:47 | pablogsal | link | issue20104 messages |
2018-05-14 13:16:47 | pablogsal | create | |
|