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/2008-August/081778.html below:

[Python-Dev] why duplicate output lines in verbose tests?

[Python-Dev] why duplicate output lines in verbose tests? [Python-Dev] why duplicate output lines in verbose tests?Antoine Pitrou solipsis at pitrou.net
Wed Aug 13 11:07:34 CEST 2008
Guido van Rossum <guido <at> python.org> writes:
> 
> On Tue, Aug 12, 2008 at 11:32 AM, Bill Janssen <janssen <at> parc.com> wrote:
> >> Is it using fork()? Threads?
> >
> > No on fork(), yes on threads.
> 
> Hmm...  I don't believe that io.py is thread-safe. 

There is an issue open for the BufferedWriter + threads problem (which is
probably what causes Bill's problem above).
http://bugs.python.org/issue3476

As Martin suggested in this issue's comments, a simple fix would be to wrap most
methods with an instance-specific mutex. I don't know how that would affect
performance.

Regards

Antoine.


More information about the Python-Dev mailing list

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