➜

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 xiang.zhang
Recipients mark.dickinson, serhiy.storchaka, vstinner, xiang.zhang
Date 2017-05-05.16:02:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494000156.42.0.327515615256.issue30281@psf.upfronthosting.co.za>
In-reply-to
Content 
I am okay to use PY_SSIZE_T_MIN. But if we are worried about future change of PY_SSIZE_T_MIN, seems we also need to change the API doc of PySlice_Unpack(). Although _PyEval_SliceIndex's comment says it clips value to -PY_SSIZE_T_MAX-1, actually it uses PyNumber_AsSize_t and clips value to PY_SSIZE_T_MIN.
History
Date User Action Args
2017-05-05 16:02:36xiang.zhangsetrecipients: + xiang.zhang, mark.dickinson, vstinner, serhiy.storchaka
2017-05-05 16:02:36xiang.zhangsetmessageid: <1494000156.42.0.327515615256.issue30281@psf.upfronthosting.co.za>
2017-05-05 16:02:36xiang.zhanglinkissue30281 messages
2017-05-05 16:02:36xiang.zhangcreate