Therein lies my suggestion. Pick a date, announce, give 3 months, then stop testing on 2.6
> -----Original Message----- > From: Donald Stufft [mailto:don...@stufft.io] > Sent: Friday, September 2, 2016 6:18 PM > To: tritium-l...@sdamon.com > Cc: distutils sig <distutils-sig@python.org> > Subject: Re: [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 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 or > little > less. > > > Right, I don’t specifically mean immediately ejecting support, but rather > deprecate and then drop along whatever the normal timeline is for project > (and stop worrying about 2.6 for new stuff). > > — > Donald Stufft > > _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
