Wait, you guys don't have a 2.6 requirement anymore?
On Wednesday, June 25, 2014 04:48:11 PM Brian Paul wrote: > On 06/24/2014 07:24 PM, Kenneth Graunke wrote: > > On Tuesday, June 24, 2014 10:30:56 AM Matt Turner wrote: > >> It was more than a year ago now [1] that we agreed to "hold these > >> patches back for a short time (maybe a month) to give people time to > >> get ready for the transition" > >> > >> In the mean time, we've struggled with Python 2.7 regressions and > >> dealt with many "this breaks with Python 2.6" comments. Is it time to > >> finally stop? > > > > Yes, please. Python 3.0 came out 5.5 years ago. Every major Linux > > distribution includes Python 3.x, and from what I've heard it's even > > installable in community repositories for enterprise distributions. It's > > easily installable on Windows. > > > > We suggested waiting about a month, and it's been a year. It's time. > > > > Making a tag or a branch prior to the switch seems reasonable to me. > > At VMware we have an environment that only has Python 2.7 and probably > won't get Python 3.0 for some time. > > Having a Python 2.7 branch of piglit would be great (err, essential). I > guess we could cherry-pick new tests to it as needed. > > -Brian > > _______________________________________________ > Piglit mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/piglit
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
