On 2016-06-09, Brett Cannon wrote: > I don't think you meant for what you said to sound insulting, > Neil, but it did feel like it upon first reading.
Sorry, I think I misunderstood what you and Nick were saying. I've experienced a fair amount of negative feedback on my idea so I'm pretty cranky at this point. Amber Brown claimed that she spent $60k of her time porting Twisted to Python 3. I think there is lots of room to make our porting tools better. Using something like modernize, 2to6, or sixer seems like a better idea than trying to improve on 2to3. I agree on that point. However, those tools combined with my modified Python 3.6 makes for a much easier migration path than going directly to Python 3.x. My runtime warnings catch many common problems and make it easy to see what needs fixing. We have a lot more freedom to put ugly, backwards compatibility hacks into this stepping stone version, rather than changing either Python 2.7.x or the main 3.x line. I'm hoping to get community contributions to add more backwards compatibility and runtime warnings. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
