Sounds good to me but would it not make more sense to remove 2.6 from our
Travis config and instead retain the CentOS / 2.6 builder in Jenkins given
that it's the only real place where 2.6 is being used?
On Wed, Dec 23, 2015 at 12:11 PM Paul Kehrer
wrote:
> Some numbers to inform this conversati
> On 23 Dec 2015, at 03:43, Alex Gaynor wrote:
>
> Hi all,
>
> I'd like to propose we formally deprecate (in our next release) and remove
> (in the release thereafter) support for Python2.6.
>
> It is no longer under support from its developers (which makes it a security
> risk), its use is
Same here, I see no issues with that.
On Wed, Dec 23, 2015 at 4:43 AM, Cory Benfield wrote:
>
>> On 23 Dec 2015, at 03:43, Alex Gaynor wrote:
>>
>> Hi all,
>>
>> I'd like to propose we formally deprecate (in our next release) and remove
>> (in the release thereafter) support for Python2.6.
>>
>
On Tue, 2015-12-22 at 22:43 -0500, Alex Gaynor wrote:
> Hi all,
>
> I'd like to propose we formally deprecate (in our next release) and remove
> (in the release thereafter) support for Python2.6.
>
> It is no longer under support from its developers (which makes it a
> security risk), its use is
