> Python 3.x will continue to change. The incompatibilities between 3.x > and 2.x will only become more numerous. If your goal is to support > 2.x, and 3.x, you'd be best supporting them separately.
I don't think that's a particularly good approach. Having a single code base for both likely reduced the maintenance burden significantly compared to a code fork. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
