Change by xloem <0xl...@gmail.com>:
--
resolution: wont fix -> out of date
___
Python tracker
<https://bugs.python.org/issue42838>
___
___
Python-bugs-li
Change by xloem <0xl...@gmail.com>:
--
resolution: out of date -> wont fix
___
Python tracker
<https://bugs.python.org/issue42838>
___
___
Python-bugs-li
xloem <0xl...@gmail.com> added the comment:
hey, I don't have the capacity to stay on this, but thanks for the attention,
time, and clear response.
there are of course other situations such as returning a resource to library
code or manual loop management, but I don't h
xloem <0xl...@gmail.com> added the comment:
I'm sorry, is this closure an error? Could you explain more how to use
asyncio.run() to clean up resources when an unhandled exception is thrown? Is
this new with a recent python improvement?
--
status: clo
xloem <0xl...@gmail.com> added the comment:
Thanks for your time.
Just a note that this is likely a docs issue if nothing else. I may never have
opened this issue if the missing functions were listed in the inspect module
documen
New submission from xloem <0xl...@gmail.com>:
The ast module has no signature information on its types. The types are
generated in a uniform way, so it should be reasonable to add
__text_signature__ or __signature__ fields to all of them at once.
--
components: Argument
New submission from xloem <0xl...@gmail.com>:
As there is no __text_signature__ nor __signature__ attribute on basic builtin
functions such as print or open, inspect.signature() cannot enumerate their
parameters.
It seems adding these might not be a complex task for somebody familia
New submission from xloem <0xl...@gmail.com>:
To handle destruction of resources especially during exceptions, it would be
nice if there were some way to provide coroutines/tasks that run at the
termination or closure of an event loop. There are a lot of api options here.
Maybe a