>>>>> "Guido" == Guido van Rossum <[EMAIL PROTECTED]> writes:
Guido> I'm not at all convinced that we should attempt to find a
Guido> solution that handles both use cases [print replacement
Guido> and i18n]; most Python code never needs i18n.
It's true that the majority of Python applications never need i18n,
because they're only used in one language. But Python applications
are mostly assembled from a large and growing set of Python-standard
and other well-known libraries. It would be very useful to keep the
barriers to i18n-ization as low as possible to make those libraries as
broadly applicable as possible.
You're talking about Python 3.0; I don't know if it can be done within
a reasonable amount of effort (and if not, too bad), but in that
planning horizon it is surely worth some effort to find a solution.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
