Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-36829: Add _PyErr_WriteUnraisableMsg() #13488

Merged
merged 1 commit into from
May 27, 2019
Merged

bpo-36829: Add _PyErr_WriteUnraisableMsg() #13488

merged 1 commit into from
May 27, 2019

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented May 22, 2019

  • sys.unraisablehook: add 'err_msg' field to UnraisableHookArgs.
  • Use _PyErr_WriteUnraisableMsg() in _ctypes _DictRemover_call()
    and gc delete_garbage().

https://bugs.python.org/issue36829

@vstinner
Copy link
Member Author

Interesting case: _PyErr_WarnUnawaitedCoroutine():

        if (PyErr_WarnFormat(PyExc_RuntimeWarning, 1,
                             "coroutine '%.50S' was never awaited",
                             ((PyCoroObject *)coro)->cr_qualname) < 0)
        {
            PyErr_WriteUnraisable(coro);
        }

The unraisable exception is logged with default "Exception ignored in: ..." message. Should we use a customized error message here?

In my PR #13490, I have to catch stderr and sys.unraisablehook to catch the warning and the unraisable exception in test_coroutines.test_unawaited_warning_when_module_broken():
https://github.com/python/cpython/pull/13490/files

@vstinner
Copy link
Member Author

@graingert @pablogsal @serhiy-storchaka: Would you mind to review this PR? I don't recall who asked me to allow to specify a custom error message :-)

@@ -1040,6 +1053,14 @@ write_unraisable_exc_file(PyObject *exc_type, PyObject *exc_value,
return -1;
}
}
else if (err_msg != NULL && err_msg != Py_None) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can avoid duplication of the code.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer to have a single PyFile_WriteString(":\n", file) call in this code path, rather than trying to factorize the code too much, to reduce the risk of failure in the hook.

@vstinner
Copy link
Member Author

I rebased my PR and merged conflicts.

* sys.unraisablehook: add 'err_msg' field to UnraisableHookArgs.
* Use _PyErr_WriteUnraisableMsg() in _ctypes _DictRemover_call()
  and gc delete_garbage().
@vstinner
Copy link
Member Author

@serhiy-storchaka: Would you mind to review the update PR?

* *object*: Object causing the exception, can be ``None``.

:func:`sys.unraisablehook` can be overridden to control how unraisable
exceptions are handled.

The default hook formats *err_msg* and *object* as:
``f'{err_msg}: {object!r}'``; use "Exception ignored in" error message
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
``f'{err_msg}: {object!r}'``; use "Exception ignored in" error message
``f'Exception ignored {err_msg}: {object!r}'``; use "Exception ignored in" error message

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It really logs f'{err_msg}: {object!r}'. _PyErr_WriteUnraisableMsg("xxx") sets err_msg to "Exception ignored xxx".

@@ -1322,13 +1351,20 @@ PyErr_WriteUnraisable(PyObject *obj)
}
}

if (err_msg_str != NULL) {
err_msg = PyUnicode_FromFormat("Exception ignored %s", err_msg_str);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hummm, why don't allowing the caller to control the full error message? (Instead of prepending "Exception ignored")

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@serhiy-storchaka asked me to do so :-) And when I started a draft change to convert existing PyErr_WriteUnraisable() to _PyErr_WriteUnraisableMsg(), I always started error messages with "Exception ignored ".

The hook allows to control the full error message. Only proposed _PyErr_WriteUnraisableMsg() enfoce "Exception ignored " prefix. We might add a new function later if needed to let control the full error message.

Copy link
Member Author

@vstinner vstinner May 26, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By the way, making "Exception ignored " prefix part of the API should reduce the size of the Python executable binary since constant strings are shorter (remove common "Exception ignored " prefix ;-)).

@vstinner
Copy link
Member Author

@serhiy-storchaka @pablogsal: So do you agree each other on "Exception ignored" prefix? :-)

@pablogsal
Copy link
Member

pablogsal commented May 26, 2019

So do you agree each other on "Exception ignored" prefix? :-)

Yup, I'm happy with it :)

@vstinner vstinner merged commit 71c52e3 into python:master May 27, 2019
@vstinner vstinner deleted the unraisable_msg branch May 27, 2019 06:57
DinoV pushed a commit to DinoV/cpython that referenced this pull request Jan 14, 2020
* sys.unraisablehook: add 'err_msg' field to UnraisableHookArgs.
* Use _PyErr_WriteUnraisableMsg() in _ctypes _DictRemover_call()
  and gc delete_garbage().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants