You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Regression in MemoryError displaying (_PyErr_Display fallback to C impl of print_exception) #110912
Seen this with real MemoryError, but I thought it was because the error handler couldn't run when out of memory. But if it produces this for an artificial MemoryError, something is very wrong.
Seen this with real MemoryError, but I thought it was because the error handler couldn't run when out of memory. But if it produces this for an artificial MemoryError, something is very wrong.
This was caused by an (incorrect) forceful fallback to the C implementation of the traceback machinery after we switched to use the Python traceback module as the main mechanism. Fixed in #110921
Activity
serhiy-storchaka commentedon Oct 16, 2023
Seen this with real MemoryError, but I thought it was because the error handler couldn't run when out of memory. But if it produces this for an artificial MemoryError, something is very wrong.
pythongh-110912: Correctly display tracebacks for MemoryError excepti…
pablogsal commentedon Oct 16, 2023
This was caused by an (incorrect) forceful fallback to the C implementation of the traceback machinery after we switched to use the Python
tracebackmodule as the main mechanism. Fixed in #110921gh-110912: Correctly display tracebacks for MemoryError exceptions us…
pythongh-110912: Correctly display tracebacks for MemoryError excepti…
pythongh-110912: Correctly display tracebacks for MemoryError excepti…