On Mon, June 28, 2010 19:06, Neil Schemenauer wrote:
> from __future__ only affects the module it appears in.  Aside from
> package install errors, I guess it doesn't buy us too much.

Of course, forgot that. Given I also agree with David's observation please
consider my +1 comment to now mean that I don't have any particular
hangups about Python version support.

> BTW, I wonder how people are interested in a Python 2.7+?  Most of
> the core Python developers want to stop the 2.x branch after 2.7.
> I'm considering making my own branch, incorporating some of the
> patches that didn't make it in 2.7.

I'm ambivalent. I'd like to move everything to 3.x but haven't quite been
able to quite do that in all our projects due to package availability
although we don't use a lot of third party packages.