A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-January/011929.html below:

[Python-Dev] should a module's thread safety be documented?

[Python-Dev] should a module's thread safety be documented? [Python-Dev] should a module's thread safety be documented?Skip Montanaro skip@mojam.com (Skip Montanaro)
Sat, 20 Jan 2001 16:31:52 -0600 (CST)
    Fred> If you can create a list of the known thread safe and known thread
    Fred> unsafe modules, I'll come up with appropriate annotations for the
    Fred> documentation.

I think that's going to be a significant undertaking, requiring examination
of a lot of Python and C code.  I'd rather approach it incrementally, which
was why I suggested the LaTeX macros.  As modules are determined to be safe
or unsafe, the appropriate safety macro could just be inserted into the
correct lib*.tex file.  It would (in my mind) expand to a stock bit of text
inserted at a standard place in the file.

Skip



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