> I wouldn't say that. For instance, I'm just starting a refactoring that will > result in getmail v.5, but I need to target Python 2.5 and up, so there's > essentially no way the code will run in Python 3.x (as another list member > posted).
That's a common myth. It is very well possible, using 2to3. You don't have to wait until you can drop 2.5 to start supporting 3.x, out of a single code base. > Why do I need to target Python 2.5? Because that's the most current default > version of Python shipped in Debian stable and various other distributions > that don't stay on the bleeding edge. getmail v.4 targeted Python 2.3 and up, > getmail v.3 targeted Python 1.5.2 and up. I may be able to target Python 2.6 > in a year or two, at which point Python 3 compatibility becomes a reasonable > goal. Are you saying that it doesn't *run* on 2.6? Why? (not sure what you mean by "targetting") Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com