On Sep 02, 2016, at 05:05 PM, Donald Stufft wrote:
>Do we think that a ~3% usage of Python 2.6 and being end-of-life'd for ~3
>years is enough to start deprecating and dropping 2.6?
Yes!
Cheers,
-Barry
pgpCalDLuc3vp.pgp
Description: OpenPGP digital signature
___
> Looking at pure usage numbers for "modern" versions of pip (6, 7, and 8)
for
downloading from PyPI I see the usage is ~3% of downloads are via Python
2.6.
And a lot of those may be CI systems for packages that still support 2.6
deprecate away!
-CHB
On Sat, Sep 3, 2016 at 1:36 PM, Danie
It would be convenient to drop 2.6 in wheel too.
On Sat, Sep 3, 2016, 14:14 Brett Cannon wrote:
> I think the fact that Python 2.6 is past EOL means it's definitely up for
> consideration. As for the 3% usage, as a trite comparison that's the amount
> of scientists who deny climate change. So IM
I think the fact that Python 2.6 is past EOL means it's definitely up for
consideration. As for the 3% usage, as a trite comparison that's the amount
of scientists who deny climate change. So IMO that suggests 2.6 is not used
enough to burden PyPA with the maintenance and those who still want to us
On 3 September 2016 at 07:47, wrote:
> Nick might have something better to say about this, but I don’t think
> catching enterprise-y linux distros like RHEL out of the blue is a good way
> to go, so even if we decide right now to drop 2.6 support, it shouldn’t
> actually ship with breaking cha
: [Distutils] When can we kill Python 2.6 support?
>
>
> > On Sep 2, 2016, at 5:47 PM, tritium-l...@sdamon.com wrote:
> >
> > Nick might have something better to say about this, but I don’t think
> catching enterprise-y linux distros like RHEL out of the blue is a good w
> On Sep 2, 2016, at 5:47 PM, tritium-l...@sdamon.com wrote:
>
> Nick might have something better to say about this, but I don’t think
> catching enterprise-y linux distros like RHEL out of the blue is a good way
> to go, so even if we decide right now to drop 2.6 support, it shouldn’t
> actua
Nick might have something better to say about this, but I don’t think catching
enterprise-y linux distros like RHEL out of the blue is a good way to go, so
even if we decide right now to drop 2.6 support, it shouldn’t actually ship
with breaking changes for like... 3 months? Maybe a little more
Kill it with fire!
On Sep 2, 2016 2:06 PM, "Donald Stufft" wrote:
> The packaging tools generally support 2.6+ and 3.(2|3)+ and that's sort of
> been
> where they've been at for a while now. I would like to think about what we
> need
> to be to start considering Python 2.6 as "too old" to suppor