Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit d9dfe02

Browse files
committed
Remove a few elderly sentences
1 parent ff8113f commit d9dfe02

1 file changed

Lines changed: 2 additions & 9 deletions

File tree

Doc/api/init.tex

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -357,15 +357,8 @@ \section{Thread State and the Global Interpreter Lock
357357

358358
The Python interpreter needs to keep some bookkeeping information
359359
separate per thread --- for this it uses a data structure called
360-
\ctype{PyThreadState}\ttindex{PyThreadState}. This is new in Python
361-
1.5; in earlier versions, such state was stored in global variables,
362-
and switching threads could cause problems. In particular, exception
363-
handling is now thread safe, when the application uses
364-
\withsubitem{(in module sys)}{\ttindex{exc_info()}}
365-
\function{sys.exc_info()} to access the exception last raised in the
366-
current thread.
367-
368-
There's one global variable left, however: the pointer to the current
360+
\ctype{PyThreadState}\ttindex{PyThreadState}. There's one global
361+
variable, however: the pointer to the current
369362
\ctype{PyThreadState}\ttindex{PyThreadState} structure. While most
370363
thread packages have a way to store ``per-thread global data,''
371364
Python's internal platform independent thread abstraction doesn't

0 commit comments

Comments
 (0)