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 mark.dickinson, ncoghlan, serhiy.storchaka, tehybel, terry.reedy
Date 2016-09-09.08:04:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Then there is a design question. I believe that after all we should expose these two new functions publicly. And the question is about function names and the order of arguments. Currently signatures are:

int _PySlice_Unpack(PyObject *r, Py_ssize_t *start, Py_ssize_t *stop, Py_ssize_t *step);
int _PySlice_EvalIndices(Py_ssize_t *start, Py_ssize_t *stop, Py_ssize_t step, Py_ssize_t length, Py_ssize_t *slicelength);

Are there suggestions for names? Perhaps the second functions should not have prefix PySlice_, since it doesn't work with slice object.
Date User Action Args
2016-09-09 08:04:22serhiy.storchakasetrecipients: + serhiy.storchaka, terry.reedy, mark.dickinson, ncoghlan, tehybel
2016-09-09 08:04:22serhiy.storchakasetmessageid: <>
2016-09-09 08:04:22serhiy.storchakalinkissue27867 messages
2016-09-09 08:04:22serhiy.storchakacreate