"Guido van Rossum" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] | On Tue, Apr 15, 2008 at 10:29 AM, Stephen J. Turnbull | <[EMAIL PROTECTED]> wrote: | > Guido van Rossum writes: | > > In Py3k we may be able to do something else though -- instead of | > > insisting on ASCII we could allow a much larger set of characters to | > > be unescaped. | > | > Yes. The implications of the PEP 3131 discussions about Unicode | > identifiers should be considered carefully. Eg, consider the | > potential of confusing ASCII 'A' with Cyrillic 'A'. I'm very unhappy | > with the idea of having Cyrillic 'A' \u-escaped when calling repr() on | > objects in a Russian's program, but I don't like the alternative of | > having "print repr(bogus)" being no more informative than "print | > bogus" in this situation any better. | | So it sounds like we're doomed if we do, and damned if we don't. Or do | I misunderstand you? Do you have a practical suggestion?
You understood the same as me. I suspect the real solution has to be language-community (and even programmer) specific, since I expect most people would like the chars they know and expect to be unescaped and others left escaped. So, perhaps there should be a unirep module, stdlib or not, used like: import unirep print(*map(unirep.russian, objects)) or even from unirep import rus_print rus_print(ojbects) # does same as above, with **kwds passed on tjr _______________________________________________ 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
