On Tue, 07 Jan 2014 11:33:55 +0100 Georg Brandl <g.brandl@gmx.net> wrote:
The proposal would be to focus entirely on addressing these roadblocks in the 3.5 version, and no other new features -- the release cycle needn't be 18 months for this one. This is similar to the moratorium for 3.2, but that one came too early for 3.x porting to really profit.
The moratorium was for alternate Python implementations IIRC, not for porting third-party libraries.
It would be very cool to have multiple projects working together with us for this, and at the release of 3.5 final, present (say) a Mercurial that works on 2.5 and 3.5.
You seem to be forgetting that we are only one part of the equation here. Unless you want to tackle Mercurial and Twisted porting yourself? Good luck with that. Regards Antoine.