On Thu, Nov 19, 2015 at 8:23 PM, Ivan Van Laningham <[email protected]>
wrote:

> Hi All--
> The trouble with requiring a minimum of 2.7.x on all platforms is that it
> would be problematic for people on CentOS, Redhat and related distros
> earlier than say, CentOS 7.  7 has 2.7, but 6 has 2.6 (and not the latest
> version, either).  Anyone who wanted to use CentOS 6 would have to install
> Python 2.7.x to use Scons.  Might not want to do it, or would go with an
> earlier version.
>

Background info: we would like backwards compatibility forever, but there
is a very large push for SCons on Python 3, and I don't think that this is
unreasonable since python 3 has been available since Dec 2008.


>
> Metta,
> Ivan
>
>
> On Thu, Nov 19, 2015 at 1:10 PM, William Blevins <[email protected]>
> wrote:
>
>>
>>
>> On Thu, Nov 19, 2015 at 4:40 PM, Bill Deegan <[email protected]>
>> wrote:
>>
>>> William,
>>>
>>> The logic I was looking at is in src/engine/SCons/Platform/win32.py
>>> Where env['SPAWN'] & env['PSPAWN'] are defined.
>>>
>>
>> Yeah. It looks like all the funky Windows api calls and spawnve
>> redefinition should be removable with 2.7 requirement.
>>
>>
>>>
>>> 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
>>>
>>>
>>
>> _______________________________________________
>> Scons-dev mailing list
>> [email protected]
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>
>
> --
> Ivan Van Laningham
> God N Locomotive Works
> http://www.pauahtun.org/
>
> http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html
> Army Signal Corps:  Cu Chi, Class of '70
> Author:  Teach Yourself Python in 24 Hours
>
> _______________________________________________
> 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

Reply via email to