Martin v. Löwis wrote: >> Will python 2.6 have something like "from future import >> unicode_string_literals" ? > > It was proposed before, I don't know whether any implementation > on that has started.
I don't see anything in the bug tracker. I'd be willing to look at it, if this is what we want to do. >> This should also solve lennart's problem. (But then py3k would need to >> support that future import, which >> is forbidden). > > Right. Of course, just removing a __future__ import is simpler than > editing all the string literals. py3k supports future imports. For example, "from __future__ import with_statement" works, and I presume it's a no-op. I did not forward port print_function, but maybe I should? Eric. _______________________________________________ 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