> So, please allow u'' in Python 3.0! With that change, my > porting/compatibility worried would be gone, and you would be able to > choose between the three porting strategies dependningon how your code > base and user base looks: 1. Clean break. 2. Syncing with 2to3, 3. > Supporting both 2.6 and 3.0.
It's as Nick says. Run 2to3. Can you please explain why that doesn't sound acceptable to you? By running 2to3, you *get* option 3; you support 2.6 and 3.0 from a single code base. Regards, Martin _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
