On 9/13/2017 12:35 PM, Ned Deily wrote:
2017-09-18 1200 UTC cutoff:
- Python 3.6.3 rc1
Also on 2017-09-18:
- Python 3.7.0 alpha 1
Have you branched these off so that further merges go into 3.6.4 and alpha2?
___
python-committers mailing list
pyt
On Sep 19, 2017, at 13:55, Terry Reedy wrote:
> On 9/13/2017 12:35 PM, Ned Deily wrote:
>
>> 2017-09-18 1200 UTC cutoff:
>> - Python 3.6.3 rc1
>
>> Also on 2017-09-18:
>> - Python 3.7.0 alpha 1
>
> Have you branched these off so that further merges go into 3.6.4 and alpha2?
Yes, they were tagg
Hi,
The macOS job has been removed from Travis CI at the beginnig of the
CPython sprint two weeks ago. Since the macOS build was removed, I'm
less annoyed by Travis CI: it seems more stable.
Are you ok to not add again the macOS job to Travis CI?
Again, my rationale is that we already have 3 mac
On Sep 19, 2017, at 15:32, Victor Stinner wrote:
>
> The macOS job has been removed from Travis CI at the beginnig of the
> CPython sprint two weeks ago. Since the macOS build was removed, I'm
> less annoyed by Travis CI: it seems more stable.
>
> Are you ok to not add again the macOS job to Tra
On Tue, 19 Sep 2017 at 15:04 Barry Warsaw wrote:
> On Sep 19, 2017, at 15:32, Victor Stinner
> wrote:
> >
> > The macOS job has been removed from Travis CI at the beginnig of the
> > CPython sprint two weeks ago. Since the macOS build was removed, I'm
> > less annoyed by Travis CI: it seems more
If you find a macOS CI platform with more capacity, please let me know :-)
Travis has been totally underwater of late, but I don't know of any
alternatives; probably because operating a fleet of macOS builders is a
giant pain. You need Apple hardware, and it turns out you can either
purchase a tra
On Sep 19, 2017, at 19:33, Alex Gaynor wrote:
>
> If you find a macOS CI platform with more capacity, please let me know :-)
>
> Travis has been totally underwater of late, but I don't know of any
> alternatives; probably because operating a fleet of macOS builders is a giant
> pain. You need
Le 20 sept. 2017 00:03, "Barry Warsaw" a écrit :
I forget though, was it a problem with macOS CI stability or general
throughput? I thought they just couldn’t keep up with the workload, in
which case it seems like we should be able to throw more resources at it,
right?
There were multiple issu
On 20 September 2017 at 12:04, Victor Stinner wrote:
> Python tests are very stable on macOS (on buildbots). So yes, it's an issue
> specific to Travis.
Although as Alex explains, that isn't really Travis CI's *fault* -
it's an artifact of the licensing design for macOS being generally
hostile to
