vs code python uses system language, not vs code display language

Environment data

• VS Code version: 1.28.2
• Extension version: 2018.10.1
• OS and version: MacOS High Sierra 10.13.6
• Python version: 3.7.0
• Type of virtual environment used: virtualenv
• Relevant/affected Python packages and their versions: none

Actual behavior

VS Code python extension uses system language in stead of vs code language settings. System language is german, vs code display language is english. vs-code-python language (in command palette) is german.

Expected behavior

VS Code python extension honors the configuration of VS Code and language is the same throughout VS Code. So, vs-code-python language should be english, as stated in vs code display language.

Steps to reproduce:

1. switch mac os to some different language than english (german in my case, this was my macs default)
2. install vs code & vs code python settings
3. change vs code Display language to english
4. type “> python” into command palette

Pythons command palette(All german except the Jupyter cell commands): Language settings of MacOS

Output of locale on the terminal:

$ locale
LANG="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_CTYPE="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_ALL=

[nikau6]

I had the exact same problem, but with the extension displaying Python’s commands ( in command palette ) in French rather than in English.

VS Code version: 1.28.2 Extension version: 2018.10.1 OS and version: Ubuntu 18.04 Python version: 3.6 Type of virtual environment used: none Relevant/affected Python packages and their versions: none

Here’s how I fixed the issue :

• Open the "locale.json" file ( Command Palette > Configure Display Language )
• Change "locale":"en" to "locale":"fr", and save.
• Restart VSCode.
• Re-open the "locale.json" file.
• Change back your locale to English : "locale":"en", and save.
• Restart VSCode.

Now the extension’s commands ( in command palette ) should be in English !

[berend]

Reinstalling python extension fixed the issue. Not sure if/how the malfunctioning state can be reached again.