The IDLE UI isn't internationalized, AFAICS.

This doesn't help when teachning Python to non-english native speakers.

While learning basic english skills is no problem for wanabe Python hackers, it isn't so for young programmers being tought informatics through Python classes.

Maybe this is a FAQ... but I couldn't discriminate enough my search terms to find prior reports :-/

Thanks in advance.

You could try to propose this on the python-ideas mailing list -- the bug tracker is for more concrete proposals.

FWIW I'm -0.5 on translating IDLE's UI.  IMHO every developer must learn English sooner or later and it's better to start using it from the beginning.  Most of text in the UI of IDLE should also be fairly simple to understand.

The idle-dev list would be even more appropriate. I have been thinking about translated help text and have been thinking about discussing it on that list when more pressing IDLE issues are disposed of.

Oliver opened thread " I18n of IDLE's interface ?" on idle-dev list.

FTR, here is a link to thread: http://mail.python.org/pipermail/idle-dev/2013-April/003254.html.
There's also a follow-up issue with a patch: #17776.

http://mail.python.org/pipermail/idle-dev/2013-April/003258.html also has a list of reasons to avoid internationalization, and 4 is one of the main reasons I'm against it.
Students already have to learn several English words anyway (e.g. keywords like if, else, for, while, class, try, except, finally, break, continue, etc.; functions like all, any, print, input, range, sorted, reversed, etc.; "concepts" like classes, functions, methods, variables, attributes, etc.).  Adding a few more (open, close, save, exit, cut, copy, paste, find, etc.) is not going to make a lot of difference anyway.

I strongly disagree with Ezio's argumentation here. If Kate and Firefox are internationalized, IDLE can very well be internationalized too.

That said, this issue can be considered a duplicate of #17776.

I responded very cautiously to #17776 in part (but not only) because I had the impression that Ezio's view was the general consensus of other developers. Antoine, since that is wrong or at least not complete right, could you record at least your +1 there?

My other reason for caution is ignorance of how gettext operates, beyond the use of _(...) to wrap strings. Hence I asked several questions on #17776 about gettext and the proposed patch. Answers there from someone, but especially another core developer, with knowledge and experience would be appreciated.

> I strongly disagree with Ezio's argumentation here. If Kate and Firefox
> are internationalized, IDLE can very well be internationalized too.

The target is different though (especially the target of Firefox).  Kate might be used mainly by developers, but it's also used by non-developers and it's probably translated also because all the KDE programs are.  Mercurial would be a better example against my point.

The problem is that the students don't understand English menus (among a number of other English things).  The two possible solutions are:
1) translate the menus to e.g. French so that the students can understand them;
2) teach enough English to the students to understand the menus.

The first solution might make students' life a bit easier at first, but it's just a short-term solution -- they will still have to deal with English in a number of other places (keywords, functions, modules, error messages, documentation).
The second solution adds a bit more overhead at first, but that will pay off pretty soon.  It also stems from the assumption that learning English is something that they will have to do (especially if they want to become developers).

I'm not strongly opposed to internationalize IDLE.  If people think that it's a good idea and are willing to invest their time doing it, I'm not going to stop them, but I reckon that this might cause a few problems whose cost, IMHO, outweighs the aforementioned short-term advantage.

> The target is different though (especially the target of Firefox).
> Kate might be used mainly by developers, but it's also used by
> non-developers and it's probably translated also because all the KDE
> programs are.  Mercurial would be a better example against my point.

Or Kdevelop, Eclipse, etc.