On 24 June 2017 at 06:14, Steve Dower wrote:
> We could improve life for everyone even more if we built Tcl/Tk once per
> update and made it a binary dependency. Nobody is updating our version of it
> regularly anyway, and this would significantly improve build time in CI.
On 6/23/2017 4:14 PM, Steve Dower wrote:
We could improve life for everyone even more if we built Tcl/Tk once per
update and made it a binary dependency. Nobody is updating our version
of it regularly anyway, and this would significantly improve build time
in CI.
On Windows, I believe
like a
“throw it all out” problem to me.
Cheers,
Steve
Top-posted from my Windows phone
From: Terry Reedy
Sent: Friday, June 23, 2017 11:44
To: python-dev@python.org
Subject: Re: [Python-Dev] Appveyor builds fail on Windows for 3.6 backports.
On 6/23/2017 2:24 PM, Zachary Ware wrote:
> On
On 6/23/2017 2:24 PM, Zachary Ware wrote:
On Fri, Jun 23, 2017 at 11:36 AM, Terry Reedy wrote:
Example: appveyor passes for
https://github.com/python/cpython/pull/2335#discussion_r123724857
Appveyor build fails for 3.6 backport
https://github.com/python/cpython/pull/2359
On Fri, Jun 23, 2017 at 11:36 AM, Terry Reedy wrote:
> Example: appveyor passes for
> https://github.com/python/cpython/pull/2335#discussion_r123724857
>
> Appveyor build fails for 3.6 backport
> https://github.com/python/cpython/pull/2359
>
Example: appveyor passes for
https://github.com/python/cpython/pull/2335#discussion_r123724857
Appveyor build fails for 3.6 backport
https://github.com/python/cpython/pull/2359
https://ci.appveyor.com/project/python/cpython/build/3.6.1+.3673
The compile and build errors have nothing to do with