On 2/8/19 9:43 AM, Bill Deegan wrote: > Check the docs on 2.7, but I'm pretty sure all pythons 3.5+ build with > threads.
Builds from python.org have built with threads for a very long time - I believe since 2.5-ish. But there's a configuration option to build without threads which someone could theoretically use - do we care about that case? That option is gone as of 3.7, fwiw - Python is officially no longer supported without full native threading support in the build (as opposed to de-facto unsupported) https://bugs.python.org/issue31370 > > On Fri, Feb 8, 2019 at 11:01 AM Mats Wichmann <[email protected]> wrote: > >> >> One of the windows scons source files uses subprocess to run vswhere, >> and it calls suprocess.communicate. This is new code and seems to be >> working fine as far as I know. >> >> Another source file calls a vcvars* batch script, and does not use >> subprocess.communicate, with the following comment: >> >> # Use the .stdout and .stderr attributes directly because the >> # .communicate() method uses the threading module on Windows >> # and won't work under Pythons not built with threading. >> >> Is that a Thing any longer? Windows Pythons not built with threading? Or >> is this a special-case that can be eliminated? >> _______________________________________________ >> Scons-dev mailing list >> [email protected] >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> > > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev > _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
