Hello,
I was recently cleaning up my buildbot, clearing space, removing
unused software, ..., and decided to remove MSVC 2010 as no supported
Python uses that compiler. Well, to my surprise, actually I forgot,
you do need MSVC 2010 *AND* 2008 to build 2.7 by default. It has been
since reinstalle
Hi Jeremy,
On Thu, Nov 3, 2016 at 1:40 PM, Jeremy Kloth wrote:
> Hello,
>
> I was recently cleaning up my buildbot, clearing space, removing
> unused software, ..., and decided to remove MSVC 2010 as no supported
> Python uses that compiler. Well, to my surprise, actually I forgot,
> you do need
Interesting - I probably would have assumed removing 2010 was safe for
2.7 as well. However, all of my 2.7 builders (XP/7/8/10) currently
have both 2008 and 2010 so any dependency on 2010 would go unnoticed.
Assuming the 2010 dependency is unintentional, or we specifically want
to test without it
Hi David,
On Thu, Nov 3, 2016 at 2:38 PM, David Bolen wrote:
> Interesting - I probably would have assumed removing 2010 was safe for
> 2.7 as well. However, all of my 2.7 builders (XP/7/8/10) currently
> have both 2008 and 2010 so any dependency on 2010 would go unnoticed.
>
> Assuming the 2010
Zachary,
> I'd like to just add a builder to your XP bot that builds in PC/VS9.0
> in addition to the regular builder in PCbuild. That will allow us to
> keep track of whether a change breaks one build or both. Once I have
> a VS9-only builder set up, if you want to remove VS2010 from any of
> y
BTW, just to follow up on my last message:
> But for third party independent builds, it appears like the 2.7.12
> documentation (https://docs.python.org/2/using/windows.html) still
> lists PCBuild and 2008.
I should have checked first, but the readme.txt in the PCBuild
directory seems to cover th
