René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[C API] Enhance PyErr_WriteUnraisable() API to pass an error message","articleBody":"### Has this already been discussed elsewhere?\n\nThis is a minor feature, which does not need previous discussion elsewhere\n\n### Links to previous discussion of this feature:\n\n_No response_\n\n### Proposal:\n\nI added a private ``_PyErr_WriteUnraisableMsg()`` API but it cannot be used in third party code, nor in stdlib extensions which try to avoid private/internal functions (like sqlite3). Moreover, ``_PyErr_WriteUnraisableMsg()`` API doesn't allow to fully customize the error message.\r\n\r\nThe limitation of ``_PyErr_WriteUnraisableMsg()`` affected PR #106674 which has to add ``; consider using ...`` in the error message which is not great.\r\n\r\n```c\r\n        _PyErr_WriteUnraisableMsg(\r\n            \"in PyMapping_HasKeyString(); consider using \"\r\n            \"PyMapping_GetOptionalItemString() or PyMapping_GetItemString()\",\r\n            NULL);\r\n```\r\n\r\n@serhiy-storchaka suggested to add an API which allows string formatting, similar to ``PyErr_Format()``.\r\n\r\n``_PyErr_WriteUnraisableMsg()`` was added in issue #81010.\r\n\r\n---\r\n\r\nBy the way, we should go through all calls to PyErr_WriteUnraisable() and add more context to more these logs easier to get for developers: give more context about what the issue is, how to fix it, where it occurred, etc.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-111086\n* gh-111455\n* gh-111507\n* gh-111580\n* gh-111643\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/vstinner","@type":"Person","name":"vstinner"},"datePublished":"2023-08-17T10:38:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/108082/cpython/issues/108082"}