Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2003-September/038005.html below:

[Python-Dev] Making python C-api thread safe

• Previous message: [Python-Dev] PyUnicode_FromEncodedObject
• Next message: [Python-Dev] Making python C-api thread safe
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Background: I'm new to Python. I just embedded Python into a 
multi-threaded application, and extended Python by callbacks as well. 
During this process I realised that Python is not internally as 
beautiful as externally. It is not thread safe. This surprised me, 
because Python is a quite young programming language. I started thinking 
how to fix this, how to make Python thread safe. Currently Python does 
not support multiprocessor machines or hyperthreading processors. It is 
only a matter of time when this has to be fixed, better soon than later.

How to make C-api thread safe: It's quite simple, in fact. Thread should 
first call

• Previous message: [Python-Dev] PyUnicode_FromEncodedObject
• Next message: [Python-Dev] Making python C-api thread safe
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4