Hi all,
To wrap a bow on this: on reviewing data from PyPI, it looks like a
significant percentage of Paramiko users are on 2.6. There's currently an
outstanding PR to port paramiko to use cryptography, and IMO that's more
important than dropping 2.6 for overall user security, so I'm going to drop
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
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 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
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
Some numbers to inform this conversation. Here are the download counts for
cryptography 1.1.2 right now (12 days of downloads):
cryptography-1.1.2.tar.gz 2015-12-10 261,761
cryptography-1.1.2-pp27-none-macosx_10_10_x86_64.whl 2015-12-10 86
