>> 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.
Neither could I. I vaguely remember having people mention it, but could not find anything, either. Perhaps you need to get approval/agreement first in a separate thread. >> Right. Of course, just removing a __future__ import is simpler than >> editing all the string literals. > > py3k supports future imports. Yes, but it won't/shouldn't support the unicode_literals __future__ import (atleast not without BDFL pronouncement). 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
