> > Those that continues working on programming will surely be exposed
> > sooner or later to formal technical English course at University or
> > similar.
> 
> The sooner they get exposed to English the better it is.  The best
> way to learn a language is by using it, and IMHO technical English
> is even easier than "normal" English (and often even than native
> language).

This sounds like wishful thinking to me. Regardless of whether it's
*better* for a fledgling programmer to learn and improve their English,
we can still improve Python right now for those who don't master English.

> > But, if they don't continue their studies, or choose a different
> > career, maybe their English skill will never be enough.
> 
> I think that nowadays anyone should learn English anyway, and the
> more you translate the more you make their lives difficult, because
> you confine them to a restricted subset of all the available
> information (this is getting off-topic though).

That will be true if translations are enabled by default, not if they
need some explicit configuration switch to be enabled.

> > Here, as you point, translation poses a new perspective, why take
> > that as a threat instead of an opportunity to bring better
> > messages?
> 
> This is a different problem though.  Python (and programming in
> general) has its own jargon, and the jargon provides a concise way
> to refer to specific concepts (e.g. tuple-unpacking).  While it
> certainly shouldn't be abused, it's often more convenient to use it.
>  Creating a new localized jargon also doesn't help, and it only
> makes things more complicated.

Well, even technical tools like gcc or Mercurial have translations
these days (not always very good ones, admittedly, but I don't see
anyone advocating for these translations to be removed).

> > At least some part should be translated too, as for example, the
> > Python Tutorial was translated by the local community to Spanish:
> > http://docs.python.org.ar/tutorial/contenido.html
> 
> But this is just a part, has not been updated in over 2 years, and
> doesn't even cover Python 3.

That's not really a problem. People teaching Python in a language
other than English can certainly create their own teaching resources
(and, ideally, share them on the Internet :-)).