[Scons-users] VS2017 and Python 3

[Bill Deegan]

Likely no release prior to py2 +py3 compat release.
I'm down to a handful of failures so we're getting close.
Likely there'll be a beta release because there've been a lot of changes to
get this far.

I'm hoping in the next week or two. (But I've said that before PY3 has had
some challenging changes especially on windows)


As far as VS2017,  if vswhere is going to be widely available an easy for
anyone to install even if they have older vs2017 install, then that'd
likely be a simpler solution.

While in the medium term I want to get the setup.py/pip issues ironed out,
for the time being depending on other python packages may complicate
installation for users.

Ideally we'd drop pywin32 as well.

BTW. Thanks for pointing out to Microsoft they made life harder for many
with their "improvements" in VS2017.

-Bill

On Wed, May 17, 2017 at 9:12 AM, Dean Glazeski <dnglaze at gmail.com> wrote:

> I'd be willing to update my pull request to use vswhere if that's the
> direction SCons wants to go.  I don't think it makes sense to have both the
> COM lookup functionality and the vswhere lookup, but I'm new to
> contributing to SCons.
>
> I'll leave the VS2017 Python 2 release question to some one else.
>
>
> // Dean
>
> On Wed, May 17, 2017 at 8:56 AM Steve Robinson <steven.robinson@
> motorolasolutions.com> wrote:
>
>> Hello,
>>
>> I see the pull request for VS2017 support, but it looks like more work is
>> required.  I've also seen the messages about Python 3 compatibility coming
>> together.  I'm curious if there are plans to have a VS2017 Python 2 release
>> before moving to Python 3?  I'm trying to plan out the upgrade process for
>> our build system.
>>
>> I was at Microsoft Build 2017 and gave feedback to the Visual C++ team
>> that while the new VS2017 installer is nice, changing the install paths and
>> removing registry keys that refer to them did not do us any favors in
>> upgrading to the latest compiler!
>>
>> Microsoft will be adding a tool to an upcoming update of VS2017 to
>> identify installer locations:
>> https://blogs.msdn.microsoft.com/heaths/2017/04/21/vswhere-
>> is-now-installed-with-visual-studio-2017/
>> I guess this might help if SCons decides not to support earlier updates.
>>
>> Anyway, let me know if there's anything I can do to help.  Thanks for all
>> the hard work.
>>
>> -Steve
>>
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20170517/c9148eeb/attachment-0001.html>