[issue38522] Py_USING_MEMORY_DEBUGGER is referenced in docs but not present in code
Change by Carlos Damázio : -- keywords: +patch nosy: +dmzz nosy_count: 3.0 -> 4.0 pull_requests: +28498 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30284 ___ Python tracker <https://bugs.python.org/issue38522> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26552] Failing ensure_future still creates a Task
Change by Carlos Damázio : -- keywords: +patch nosy: +dmzz nosy_count: 4.0 -> 5.0 pull_requests: +28501 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30287 ___ Python tracker <https://bugs.python.org/issue26552> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46194] Wrong base class for transport returned by loop.create_datagram_endpoint()
Change by Carlos Damázio : -- keywords: +patch nosy: +dmzz nosy_count: 2.0 -> 3.0 pull_requests: +28505 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30291 ___ Python tracker <https://bugs.python.org/issue46194> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22859] unittest.TestProgram.usageExit no longer invoked
Change by Carlos Damázio : -- keywords: +patch nosy: +dmzz nosy_count: 1.0 -> 2.0 pull_requests: +28507 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30293 ___ Python tracker <https://bugs.python.org/issue22859> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35812] Don't log an exception from the main coroutine in asyncio.run()
Carlos Damázio added the comment: Hey, Andrew. I'd like to work on the issue, if anyone else hasn't done it yet. -- nosy: +Carlos Damázio ___ Python tracker <https://bugs.python.org/issue35812> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21879] str.format() gives poor diagnostic on placeholder mismatch
Carlos Damázio added the comment:
I've noticed this issue is quite not active, but I'm up on participating in it
if anyone is doing it already. Since then, this issue still persists:
>>> '{1}'.format()
Traceback (most recent call last):
File "", line 1, in
IndexError: tuple index out of range
Reading further, I agree that improving the message is suitable. We should
leave the Index Exception while changing the text to "Replacement index %d out
of range for positional args tuple". Even though I find it quite extent for an
exception message, I guess it couldn't be any other way, unless someone gives a
better suggestion.
--
nosy: +dmzz
___
Python tracker
<https://bugs.python.org/issue21879>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21879] str.format() gives poor diagnostic on placeholder mismatch
Carlos Damázio added the comment: Ops, someone already patched it! Sorry guys. -- ___ Python tracker <https://bugs.python.org/issue21879> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
