[Scons-dev] Would requiring Python 2.7.4 or above be a problem for future release?

William Blevins wblevins001 at gmail.com
Wed Nov 18 17:00:32 EST 2015


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 <dragon512 at live.com> 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 <bill at baddogconsulting.com>
> Sent: ‎11/‎18/‎2015 12:20 PM
> To: SCons users mailing list <scons-users at scons.org>; SCons developer list
> <scons-dev at scons.org>
> 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
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20151118/e1eb9018/attachment-0001.html>


More information about the Scons-dev mailing list