A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2014-April/134365.html below:

[Python-Dev] API and process questions (sparked by Claudiu Popa on 16104

[Python-Dev] API and process questions (sparked by Claudiu Popa on 16104 [Python-Dev] API and process questions (sparked by Claudiu Popa on 16104Ned Deily nad at acm.org
Mon Apr 28 20:43:05 CEST 2014
In article 
<CA+OGgf4weBk1NsXBSqi1g7tDE-=7rfkzd5bZn1MXiHWSggECEQ at mail.gmail.com>,
 "Jim J. Jewett" <jimjjewett at gmail.com> wrote:
> As Claudiu pointed out, processes=1 should really mean 1 worker
> process, which is still different from "do everything in the main
> process".  I'm not sure that level of control is really worth the
> complexity, but I'm not certain it isn't.

For regrtest, there is an important difference between "do everything in 
the main process" and "do one test at a time in a subprocess", namely 
the inadvertent global side-effects that running some tests have on 
other tests.  The latter option is much safer and gives more 
reproducible test results.  For compileall, I don't think there is a big 
difference between the two cases such that the regrtest semantics need 
to be followed.

-- 
 Ned Deily,
 nad at acm.org

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