Open rabyj opened 3 months ago
Hey @rabyj 👋
thanks for taking the time to report this!
in Jupyter Lab, the numbers line up for me:
If vscode is showing numbers differently, then maybe we need ask them to reconsider their numbering?
We could introduce an option in nbQA to let the user choose, although:
Thanks for the fast reply @MarcoGorelli
Isn't that the execution number though, which will change a lot when using a notebook? afaik Jupyter Lab does not actually possess cell numbers. I'm referring to the number on the bottom right, cell X of Y.
true, I think I was assuming that people would be checking notebooks into version control after having done "restart and run all" (say, if they're using notebooks for documentation)
Issue
When getting warnings from nbqa-pylint, e.g.
notebook.ipynb:cell_XX:Y:Z: C0206: Consider iterating with .items() (consider-using-dict-items)
, the cell number does not refer to the same number as in vscode. cell_XX does not count markdown cells, rendering the message confusing (and way less useful in large notebooks with lots of markdown)Joining an example notebook as exported script, since github won't allow me to joint it directly.
I run
pre-commit run nbqa-pylint
on the staged notebook to generate warnings.System information
Notebook exported as Python script
Side question I couldn't find an answer to: Is there a way to force nbqa-pylint to show the context of the error and/or cell content, instead of just showing the warning with cell number? I can file it somewhere else (where?) if this is inappropriate.