Internals of exceptions on ThreadState `_ts` struct have moved
See original GitHub issuehttps://github.com/python/cpython/commit/ae3087c6382011c47db82fea4d05f8bbf514265d / https://bugs.python.org/issue25612 / https://github.com/python/cpython/pull/1773 re-arranged how exception information is stored and moved exc_type
, exc_value
, and exc_tracback
into a _err_stackitem
struct pointed to by exc_info
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Internals of Exceptions - Adam Furmanek - YouTube
You know how to throw and catch exception. But do you know how are they implemented internally? Do you know what is SEH,...
Read more >Threading in C# - Part 2 - Basic Synchronization
In this section, we'll start with the lock construct and then move on to Mutex and semaphores (for nonexclusive locking). Later, we'll cover ......
Read more >Changelog — Python 3.11.1 documentation
gh-97612: Fix a shell code injection vulnerability in the get-remote-certificate.py example script. The script no longer uses a shell to run openssl commands....
Read more >C++ Tutorial: Multi-Threaded Programming - Terminology 2020
A thread uses the same address space of a process. A process can have multiple threads. A key difference between processes and threads...
Read more >thesis-thread-safe-data-representations-in-dynamic ...
Since data structures cannot be modified, these languages re- ... 1Under the Java Memory Model, plain memory accesses can be moved inside a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You are right, there was a left-over. Thanks for insisting.
The syntax fix was correct. The question is rather whether the original implementation was semantically correct. Could well be that there are more/other things to do here now.
Besides, to verify that the expected Cython version was used to generated a specific C file, look at the version marker in the first line of the file.
head -1 somefile.c
is a useful remote debugging helper here, for those who have to deal with users who complain about failures even after installing the latest Cython.