You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for this awesome extension which makes life much easier, and I am sorry if there is another opened issue about this.
My issue is the same as that one : #188 (which is closed)
On my Jupyter Notebook, triggering formatting with Black will remove the trailing semi-colon.
For example, on a Python cell with : plt.show();, the black extension commands would remove the trailing whitespace which has a meaning on Jupyter Notebook.
Reproduced on v2024.3.11371020 (pre-release) and v2024.2.0 ms-python.black-formatter versions (vscode 1.89.1).
Note the trailing semi-colons are not removed if I format my notebook with the black package in command line (without using ms-python.black-formatter), but it is less convenient (v24.4.2).
Is this supposed to be fixed ? (as the above issue was closed)
Or is there a workaround that can be done on the settings.json ?
Thank you for your reply.
The text was updated successfully, but these errors were encountered:
vimchun
added
the
bug
Issue identified by VS Code Team member as probable bug
label
May 27, 2024
Hello,
First, thank you for this awesome extension which makes life much easier, and I am sorry if there is another opened issue about this.
My issue is the same as that one : #188 (which is closed)
On my Jupyter Notebook, triggering formatting with Black will remove the trailing semi-colon.
For example, on a Python cell with :
plt.show();
, the black extension commands would remove the trailing whitespace which has a meaning on Jupyter Notebook.Reproduced on v2024.3.11371020 (pre-release) and v2024.2.0 ms-python.black-formatter versions (vscode 1.89.1).
Note the trailing semi-colons are not removed if I format my notebook with the black package in command line (without using ms-python.black-formatter), but it is less convenient (v24.4.2).
Is this supposed to be fixed ? (as the above issue was closed)
Or is there a workaround that can be done on the settings.json ?
Thank you for your reply.
The text was updated successfully, but these errors were encountered: