Yury Selivanov <yseliva...@gmail.com> added the comment:
@Mark > Mark Shannon wrote: I don't think [the C-API function] should be public, as a > possible further improvement is to stop passing exceptions through a side > channel, but in result. Maybe we don't want to do that, but lets' not add to > the (already rather large) C-API. Yeah, we can add it as a "private" function, I'm not entirely opposed to that. But... it would be great if Cython and C code could still depend on it and use it. And then... why should it be private? The corresponding Python API "gen.send()" and "gen.throw()" is public, why can't the C API be public too? We will not fundamentally change generators (it would be a major backwards incompatible change), so committing to a good C API sounds reasonable. @Mark > Remember that PyIter_Next() is pretty much the same, though, and it has the > standard "return PyObject*" interface. These two would diverge then. Maybe we should call it `_PyIter_Send()`? While `.send()` is mostly about coroutines, regular generators have the method too, and it would be weird to call `_PyCoro_Send` on a generator object. @Vladimir > PYGEN_ERROR | NULL | Regular PyErr_* functions should be used to work > with error case Correct. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41756> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
