[Python-Dev] Replacement for print in Python 3.0

Stephen J. Turnbull stephen at xemacs.org
Wed Sep 7 11:23:16 CEST 2005

>>>>> "Guido" == Guido van Rossum <guido at python.org> writes:

    Guido> Sure, we must provide good i18n support. But the burden on
    Guido> users who don't need i18n should be negligeable; they
    Guido> shouldn't have to type or know extra stuff that only exists
    Guido> for the needs of i18n.

Agreed.  That's best for i18n, too, if we can arrange a batteries-
included approach to i18n at the same time.

    >> 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.

    Guido> There seem to be many people interested in finding this
    Guido> solution; I see it as my task (among others) to make sure
    Guido> that their solution doesn't negatively affect the life of
    Guido> the majority of users who don't need it.

Convenient as a Python optimized for i18n would be for me personally,
I agree with that, too.  But you wrote, "I'm not at all convinced that
we should attempt to find a solution that handles both use cases; most
Python code never needs i18n."  And now, "That's too bad, [those who
need i18n] will have to apply some global transformation to their
code."  It sounds to me like you have already decided that i18n
applications will have to use a different way.  But print-ng looks
like becoming the OOWTDI for a lot of applications.  IMO it's just too
early to give up on print-ng becoming the one obvious way to do it for
a lot of i18n apps, too.

I realize that maybe it won't be solved for Python 3.0.  Just, please
don't close the door on it yet!

    Guido> Remember YAGNI!

For-values-of-Y=I-A=am-ly y'rs,

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.

More information about the Python-Dev mailing list