On Tue, 21 Jul 2015 18:59:00 +0800 Ben de Groot wrote:
> On 20 July 2015 at 17:27, Jason Zaman wrote:
> > On Mon, Jul 20, 2015 at 10:39:25AM +0200, Dirkjan Ochtman wrote:
> >> On Mon, Jul 20, 2015 at 6:03 AM, Ben de Groot wrote:
> >> > I would like to hear from the other team members, yes.
> >>
>
On Tuesday 21 July 2015 18:59:00 Ben de Groot wrote:
> On 20 July 2015 at 17:27, Jason Zaman wrote:
> > On Mon, Jul 20, 2015 at 10:39:25AM +0200, Dirkjan Ochtman wrote:
> >> On Mon, Jul 20, 2015 at 6:03 AM, Ben de Groot wrote:
> >> > I would like to hear from the other team members, yes.
> >>
>
On 20 July 2015 at 17:27, Jason Zaman wrote:
> On Mon, Jul 20, 2015 at 10:39:25AM +0200, Dirkjan Ochtman wrote:
>> On Mon, Jul 20, 2015 at 6:03 AM, Ben de Groot wrote:
>> > I would like to hear from the other team members, yes.
>>
>> I have sympathy towards those who are asking for only one Pytho
On Mon, Jul 20, 2015 at 10:39:25AM +0200, Dirkjan Ochtman wrote:
> On Mon, Jul 20, 2015 at 6:03 AM, Ben de Groot wrote:
> >> I don't see any strong technical reason to switch from python2 +
> >> python3 to python2-only enabled. Some people don't like having two
> >> versions of python installed --
On Mon, Jul 20, 2015 at 6:03 AM, Ben de Groot wrote:
>> I don't see any strong technical reason to switch from python2 +
>> python3 to python2-only enabled. Some people don't like having two
>> versions of python installed -- that's about the gist of it.
>
> Indeed, there is no strong technical re
Le 19/07/2015 18:42, Ben de Groot a écrit :
> I would like to note that we only have around 50 packages that require
> python3, while the majority requires python2, and the remainder will
> function with either.
How far are we from building a python3-only stage3? Are there any major
blockers? Woul
On 20 July 2015 at 02:31, Mike Gilbert wrote:
> On Sun, Jul 19, 2015 at 12:42 PM, Ben de Groot wrote:
>> On 20 July 2015 at 00:03, Mike Gilbert wrote:
>>> If there are no objections, I would like to enable python3.4 by
>>> default on Saturday, July 25. That means making the following change:
>>>
On 20 July 2015 at 01:01, Anthony G. Basile wrote:
> On 7/19/15 12:42 PM, Ben de Groot wrote:
>>
>> On 20 July 2015 at 00:03, Mike Gilbert wrote:
>>>
>>> If there are no objections, I would like to enable python3.4 by
>>> default on Saturday, July 25. That means making the following change:
>>>
>
On Sun, Jul 19, 2015 at 12:42 PM, Ben de Groot wrote:
> On 20 July 2015 at 00:03, Mike Gilbert wrote:
>> If there are no objections, I would like to enable python3.4 by
>> default on Saturday, July 25. That means making the following change:
>>
>> profiles/base/make.defaults:
>> PYTHON_TARGETS="p
On 7/19/15 12:42 PM, Ben de Groot wrote:
On 20 July 2015 at 00:03, Mike Gilbert wrote:
If there are no objections, I would like to enable python3.4 by
default on Saturday, July 25. That means making the following change:
profiles/base/make.defaults:
PYTHON_TARGETS="python2_7 python3_4"
I woul
On 20 July 2015 at 00:03, Mike Gilbert wrote:
> If there are no objections, I would like to enable python3.4 by
> default on Saturday, July 25. That means making the following change:
>
> profiles/base/make.defaults:
> PYTHON_TARGETS="python2_7 python3_4"
I would like to note that we only have ar
On Sun, Nov 23, 2014 at 8:56 PM, Mike Gilbert wrote:
> Just a heads-up: I have reverted PYTHON_TARGETS to contain python2_7
> and python3_3 (removing python3_4).
>
> The stable tree is not quite ready for python3_4; there are many
> packages that need to have python3_4 added to PYTHON_COMPAT, and
12 matches
Mail list logo
