Re: windows and non-thread Pythons
Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org> Fri, 8 Feb 2019 11:43:26 -0500
| Newsgroups | gmane.comp.programming.tools.scons.devel |
|---|---|
| Message-ID | <CAEyG4CHH_3Cw=Hyvhea4k_czRxgYNu4DDHNeY=K8wfUc1BFuTQ@mail.gmail.com> |
Check the docs on 2.7, but I'm pretty sure all pythons 3.5+ build with threads. 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