I don't mind having it around. I'm just wondering if it is worth the bother of keeping it "up-to-date." Currently "stackless" development is don thus: 1) Submit commit to 2.7 2) graft to 3.2 3) merge to 3.3
If we stop supporting 3.2 this will currently change to: 1) submit to 2.7 2) graft to 3.3 Once we get 3.4 / default into the fold, this changes to: 1) submit to to 2.7 2) graft to 3.3 4) merge to default Once 2.8 is there, then the extra step of 1.4) merge to 2.8 Dropping 3.2 support will remove an extra step out of the integration dance. Which is why I'm wondering if anyone is using stackless 3.2-slp. Is there any reason for people to use 3.2 when 3.3. has been around for a while? Is anyone using stackless 3.x at all? Given that perhaps 2% of the ecosystem are using 3.x, and that an unguessable, but small, fraction of the ecosystem are using stackless, then this multiplies into a very small value, particularly for 3.2 :) K :) > -----Original Message----- > From: [email protected] [mailto:stackless- > [email protected]] On Behalf Of Richard Tew > Sent: 6. janúar 2014 18:03 > To: The Stackless Python Mailing List > Subject: Re: [Stackless] Upcoming Stackless releases > > It does no harm to leave 3.2 around, I think. If it were time to close it, > you > wouldn't need to ask. > > If our 3.4 is really cpython's default, then we should rename it for > consistency. > _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
