William, The logic I was looking at is in src/engine/SCons/Platform/win32.py Where env['SPAWN'] & env['PSPAWN'] are defined.
I missed seeing the file you reference, but indeed if we're at 2.7, then this file should no longer be necessary? -Bill On Wed, Nov 18, 2015 at 2:00 PM, William Blevins <[email protected]> wrote: > If I understand correctly, the idea here is to move away from a custom > Popen implementation in "src/engine/SCons/compat/_scons_subprocess.py" to > using the Python subprocess implementation. > > Unless that file is no longer used and we are still generating a warning > for no reason. > > On Wed, Nov 18, 2015 at 9:33 PM, Jason Kenny <[email protected]> wrote: > >> I am unclear on why this version. Part has only been using ctypes since >> 2.6 for everything win32 >> >> Why would this version of python be the needed. I would think everything >> should be easy to switch. >> >> Jason >> >> ------------------------------ >> From: Bill Deegan <[email protected]> >> Sent: 11/18/2015 12:20 PM >> To: SCons users mailing list <[email protected]>; SCons developer >> list <[email protected]> >> Subject: [Scons-dev] Would requiring Python 2.7.4 or above be a problem >> for future release? >> >> Greetings, >> >> To drop the requirement for pywin32, it may be necessary to require >> python 2.7.4 or above. >> >> Will this cause anyone significant issues? >> >> _Bill >> >> _______________________________________________ >> 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
