Michael Aye

> python -c "import logging; logging.basicConfig(level='INFO'); import black" @AlJohri This workaround does not work: ```bash $ python -c "import logging; logging.basicConfig(level='INFO'); import black" INFO:blib2to3.pgen2.driver:Generating grammar tables from /luna4/maye/miniconda3/envs/py38/lib/python3.8/site-packages/blib2to3/Grammar.txt INFO:blib2to3.pgen2.driver:Writing grammar...

@sorin-ionescu It's still not in external, is it? At least I don't get it during update.

Same here, `-n` is not properly parsed, `--dry-run` is fine. Cost me half an hour to see what's going wrong. :(

bump (the irony! ;)

This would be great! In the mean time, is there a work-around I could do? Is it somehow possible to use Box's ingenious dotted nested access to update something in...

for me the conda env info is completely gone, probably eaten by the time display:

correction: It's there now, but appears on the left even when I unset `CONDA_LEFT_PROMP`:

oh, pity. then `changes` is a no go for me, as I'm die-hard conda user. Thanks for the fast reply.

I'm confused, why is this issue here and not in python-lsp-server? I thought `jupyterlab-lsp` is language agnostic?

I would, but the whole code formatting story inside jlab has become a completely obfuscated story with too many settings locations, clients-upon-servers, knobs to turn, some formatter's options supported, some...