On 29.06.2017 05:19, Scott Kitterman wrote:
> On Friday, June 23, 2017 02:09:34 PM Scott Kitterman wrote:
>> On Saturday, June 17, 2017 04:20:27 AM Scott Kitterman wrote:
>>> Python3.6 is already in Unstable and I expect to see it in Testing soon
>>> after Stretch is released.
>>>
>>> I've just now
On Wednesday, July 05, 2017 10:24:26 AM Emilio Pozuelo Monfort wrote:
> Hi Scott,
>
> On 05/07/17 06:25, Scott Kitterman wrote:
> > On Wednesday, June 28, 2017 11:19:37 PM Scott Kitterman wrote:
> >> On Friday, June 23, 2017 02:09:34 PM Scott Kitterman wrote:
> >>> On Saturday, June 17, 2017 04:20
Hi Scott,
On 05/07/17 06:25, Scott Kitterman wrote:
> On Wednesday, June 28, 2017 11:19:37 PM Scott Kitterman wrote:
>> On Friday, June 23, 2017 02:09:34 PM Scott Kitterman wrote:
>>> On Saturday, June 17, 2017 04:20:27 AM Scott Kitterman wrote:
> ...
As a reminder (and for anyone new) we'll
On Wednesday, June 28, 2017 11:19:37 PM Scott Kitterman wrote:
> On Friday, June 23, 2017 02:09:34 PM Scott Kitterman wrote:
> > On Saturday, June 17, 2017 04:20:27 AM Scott Kitterman wrote:
...
> > > As a reminder (and for anyone new) we'll do the transition to python3.6
> > > in three stages:
> >
On Friday, June 23, 2017 02:09:34 PM Scott Kitterman wrote:
> On Saturday, June 17, 2017 04:20:27 AM Scott Kitterman wrote:
> > Python3.6 is already in Unstable and I expect to see it in Testing soon
> > after Stretch is released.
> >
> > I've just now uploaded a version of python3-defaults to Exp
On 24 June 2017 at 06:09, Scott Kitterman wrote:
> On Saturday, June 17, 2017 04:20:27 AM Scott Kitterman wrote:
> > Python3.6 is already in Unstable and I expect to see it in Testing soon
> > after Stretch is released.
> >
> > I've just now uploaded a version of python3-defaults to Experimental
On Saturday, June 17, 2017 04:20:27 AM Scott Kitterman wrote:
> Python3.6 is already in Unstable and I expect to see it in Testing soon
> after Stretch is released.
>
> I've just now uploaded a version of python3-defaults to Experimental that
> adds python3.6 as as supported (but not default) pyth
On Jun 17, 2017, at 04:20 AM, Scott Kitterman wrote:
>Last time I compared my understanding of the Buster schedule with the
>python3.7 schedule, I recall concluding that we'd likely be on python3.6 for
>the Buster release (not sure that's still true). If so, we only have to do
>this once this cyc
On Friday, June 16, 2017 10:27:34 PM Steve Langasek wrote:
> On Fri, Jun 16, 2017 at 10:23:06PM -0700, Steve Langasek wrote:
> > [1] pytables is a failure specific to Ubuntu armhf buildds which raise
> > SIGBUS, this should not affect Debian. python-astropy rebuilds with no
> > problem, but doesn'
On Fri, Jun 16, 2017 at 10:23:06PM -0700, Steve Langasek wrote:
> [1] pytables is a failure specific to Ubuntu armhf buildds which raise
> SIGBUS, this should not affect Debian. python-astropy rebuilds with no
> problem, but doesn't pick up python3.6 support.
To clarify: python-astropy builds an
On Sat, Jun 17, 2017 at 04:20:27AM +, Scott Kitterman wrote:
> Python3.6 is already in Unstable and I expect to see it in Testing soon
> after Stretch is released.
> I've just now uploaded a version of python3-defaults to Experimental that
> adds python3.6 as as supported (but not default) pyt
Python3.6 is already in Unstable and I expect to see it in Testing soon after
Stretch is released.
I've just now uploaded a version of python3-defaults to Experimental that adds
python3.6 as as supported (but not default) python3. If you have binary
extensions packaged, please start testing wi
12 matches
Mail list logo
