On 05/22/2015 06:35 PM, Terry Reedy wrote:
Not supporting 2010 should be contingent on the availability of just
the 2015 compiler -- as is possible for the 2010 compiler -- without
several gigabytes of extra fluff. This is still in the future.
Perhaps, but that's not what it says in the sourc
On 5/22/2015 6:53 PM, Larry Hastings wrote:
I'll answer my own question here. According to PCbuild/readme.txt:
This script will use the env.bat script to detect one of Visual
Studio 2015, 2013, 2012, or 2010, any of which may be used to build
Python, though only Visual Studio 2015
On Fri, May 22, 2015 at 05:24:53PM -0700, Larry Hastings wrote:
> On 05/22/2015 05:11 PM, Trent Nelson wrote:
> >Do we still support WS2K3? (Can I even install VS 2015 on that? I would
> >have thought not.)
>
> According to PCbuild/readme.txt, no. It says:
>
>This directory is used to build
On 05/22/2015 05:11 PM, Trent Nelson wrote:
Do we still support WS2K3? (Can I even install VS 2015 on that? I
would have thought not.)
According to PCbuild/readme.txt, no. It says:
This directory is used to build CPython for Microsoft Windows NT
version 6.0 or higher (Windows Vista, Wi
On Fri, May 22, 2015 at 10:06:48PM +, Steve Dower wrote:
> The Windows 7 buildbots are failing on test_asdl_parser, but I have no
> idea why – the test works for me just fine. Yury and Benjamin made the
> most recent changes to Python.asdl, but I have no idea what effect
> they would have here,
*From:*Larry Hastings [mailto:la...@midwinter.com] *On Behalf Of
*Larry Hastings
*Sent:* Friday, May 22, 2015 1530
*To:* Steve Dower; Python Dev; python-committers
*Cc:* Yury Selivanov; Benjamin Peterson
*Subject:* Re: [python-committers] Can we clean up the buildbots please?
Is MSVS 2015 the
Two of them are useless (x86 Windows Server 2003 [SB] and x86 XP-4, to be
precise), but the fact that everything other than test_asdl_parser passes is a
very valuable signal. AMD64 Windows 7 SP1 is also using the correct compiler.
Since some of our core developers are yet to upgrade, I’m not aga
On Sat, May 23, 2015 at 12:53 AM, Chris Barker wrote:
> On Fri, May 22, 2015 at 2:33 PM, Larry Hastings wrote:
>>
>> On 05/22/2015 02:29 PM, Chris Barker wrote:
>>
>> Is it too late to get the isclose() code (PEP 485) into 3.5?
>
> ...
>>
>> Hopefully you can find a core dev familiar enough wit
On 05/22/2015 03:06 PM, Steve Dower wrote:
The Windows 7 buildbots are failing on test_asdl_parser, but I have no
idea why – the test works for me just fine. Yury and Benjamin made the
most recent changes to Python.asdl, but I have no idea what effect
they would have here, or why it’s Windows
The Windows 7 buildbots are failing on test_asdl_parser, but I have no idea why
– the test works for me just fine. Yury and Benjamin made the most recent
changes to Python.asdl, but I have no idea what effect they would have here, or
why it’s Windows only.
The WS2K3 machine needs a reboot – I p
Right now we have eight online buildbots for Python trunk. Of those,
currently *six* are reporting errors in either the compile or test phases.
http://buildbot.python.org/all/waterfall?category=3.x.stable
There's one platform ("AMD64 Snow Leop") where the failures are sporadic
"stack ov
On 05/22/2015 02:29 PM, Chris Barker wrote:
Is it too late to get the isclose() code (PEP 485) into 3.5?
I posted the code here, and got a tiny bit of review, but have not yet
merged it into the source tree -- and don't know the process for
getting it committed to the official source.
So --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 13.05.15 um 09:59 schrieb Larry Hastings:
> When you say "branch testing", you mean "running the buildbots
> against it"? Right now the UI for doing that is pretty clunky.
> Kicking off a build against a server-side clone (iirc) requires
> clicking
Howdy howdy. It's-a me, Larry, your friendly neighborhood Python 3.5
Release Manager.
Somewhere around 2 or 3pm tomorrow I expect to tag Python 3.5 beta 1.
We'll actually release beta 1 on Sunday, once the binary installers are
all built.
Beta 1 is also feature-freeze, meaning no new fe
14 matches
Mail list logo
