Support for project-level config files

Elevator Pitch

Filtering the relevant diagnostics should be as easy as git cloneing a repo with a project-level setup.cfg.

Motivation

We are working collaboratively on a repo of Jupyter notebooks. When working on a Python project, we are accustomed to have a setup.cfg that configures the linters for the whole project. The same convenience should be in place for this repo of notebooks.

Design Ideas

A difficulty that I see is that at the moment jupyter-lsp does not seem to have a concept of “project boundary”. Therefore it might be an issue to find project-level configuration files.

Possible solutions:

• simply walk up the file tree a number of levels
• use git rev-parse --show-toplevel if available and find config files there and in any sub-directories

[krassowski]

I would such placement of setup.cfg to work. Feel free to open an issue in https://github.com/python-lsp/python-lsp-server; if you feel comfortable with Python you might be the best person to debug this at the moment, I don’t believe any one else touched this code recently.

[StefanBrand]

Out of curiosity what would happen if you create ~/.jupyter/jupyter_notebook_config.py or ~/.jupyter/jupyter_server_config.py with:

I tried both config files and it does not seem to change anything. The directory that appears when JupyterLab is ready is still /home/jovyan.