RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII

[joslarson]

RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII

[sebw]

Same problem here. Exact same stacktrace.

Black works from the command line:

$ python3 -m black -l 88 .
reformatted /Users/sw/Desktop/test.py

[joslarson]

@octohedron @sebw Sorry for the slow response guys! I messed up my notification settings and wasn't getting notified about issues on this repo.

This seems related to #9 which I published a hacky fix for a while back, but I'm not sure why it's not working for you.

TLDR: it's actually an issue with VS Code

Some workarounds are mention in #9 such as launching VS Code from your terminal instead of the dock/finder or hacking your black path to set the locale.

Also, Black formatting support just landed in the latest official Python extension, so you might want to switch to that, though I'm unsure whether it will fix your issue. My plan all along has been to deprecate this extension once the official Python extension added support for Black. Let me know if there's any reason I shouldn't go ahead with that course of action.

[joslarson]

@blackrobot The only work around that I can figure out is to launch vscode from your teminal using the code command: https://code.visualstudio.com/docs/setup/mac#_launching-from-the-command-line

When you do that VS Code will inherit your system's locale settings. That's how I work anyways, so I've never run into this issue.

[joslarson]

I'm going to go ahead close this since, from what I understand, switching to the official Python extension solves the issue, and I'm going to move forward with deprecating this extension. Thanks!

[blackrobot]

@joslarson:

from what I understand, switching to the official Python extension solves the issue

Unfortunately, this does not seem to be the case for me, as I wrote in microsoft/vscode-python#1980.

Do you know what change in the official repos should have fixed this issue?

And, would you have any suggestions for working around this bug while using the official extension?

In the meantime, your extension is still working – thank you!

[joslarson]

@blackrobot thanks for the info, I've reopened this (I don't know of any specific changes, no). With the official extension have you tried setting your blackPath to LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 /Users/damon/.pyenv/versions/3.6.5/bin/black?