On Thu, Nov 5, 2009 at 5:31 PM, Terry Reedy <tjre...@udel.edu> wrote: > Steven D'Aprano wrote: > >> I've played around with 3.0, and I've read the What's New for 3.1 (and am >> installing 3.1 now), and while the changes look nice, I'm not sure that >> they're nice enough to deal with the pain of 2to3 migration. > > I am in a different position since I did not have current code that would > need migrating. > >> So how about that, 3.1 fans? What are the most compelling reasons for you >> that convinced you to change? > > I am writing a book on algorithms that uses a subset of 3.1 as the algorithm > language. It it simply cleaner and easier to explain to people not already > familiar with the quirks of 2.x. One small but important-to-me example. I do > not need to put 'from __future__ import integerdivision' (or whatever the > incantation is) as the top of files. Hence I do not need to waste energy > (mime and readers) explaining furture imports and the specifics of the old > versus new meaning of int/int.
I agree. Most of my code is primarily mathematical, and while I personally see the move away from functional programming techniques as a minor misstep, the cleanliness of it all more than makes up for that. Geremy Condra -- http://mail.python.org/mailman/listinfo/python-list