[issue35456] asyncio.Task.set_result() and set_exception() missing docstrings (and Liskov sub. principle)

Yury Selivanov added the comment: -1 on this; there is no clear win in doing this refactoring, only a hard to estimate chance of making a regression. Yahya, feel free to tackle other asyncio bugs or improvements, this one is just something that we aren't comfortable doing right now.

[issue35456] asyncio.Task.set_result() and set_exception() missing docstrings (and Liskov sub. principle)

INADA Naoki added the comment: > One way to deal with that would be to let a Task have a Future. > "Prefer composition over inheritance" as they say. > > I want to work on PR for this if nobody goes against it... I'm not against it, unless it doesn't have backward incompatibility or

[issue35456] asyncio.Task.set_result() and set_exception() missing docstrings (and Liskov sub. principle)

Change by Ned Deily : -- components: +asyncio nosy: +asvetlov, yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35456] asyncio.Task.set_result() and set_exception() missing docstrings (and Liskov sub. principle)

New submission from Yahya Abou Imran : In asyncio.Task help: | set_exception(self, exception, /) | Mark the future done and set an exception. | | If the future is already done when this method is called, raises | InvalidStateError. | | set_result(self, result,