Check whether imports are at top of notebook

[redeboer]

Since #8872, E402 works per cell in Jupyter notebooks. However, in some projects, you may want to have the imports in one cell on the top of the notebook (e.g. to avoid cluttering code cells further below).

Would it be an idea to either introduce:

1. a new lint.pycodestyle setting like imports-at-top-of-notebook (defaults to False)?
2. a new E403 rule that is specifically for notebooks that works at notebook level? This is a variant of what @dhruvmanila suggested in Update E402 to work at cell level for notebooks #8872 (comment).

I would suggest 1., to avoid potential rule code clashes (e.g. #2194).

[dhruvmanila]

Thanks for the feature request. I think this is a useful feature.

We also discussed about providing a dedicated code action to move all imports in a Jupyter Notebook to a dedicated code cell at the top. Just want to confirm whether this request is to move the imports to a dedicated code cell at the top or just to the first code cell (might contain other Python code) in the notebook.

[redeboer]

We also discussed about providing a dedicated code action to move all imports in a Jupyter Notebook to a dedicated code cell at the top.

Awesome!

Just want to confirm whether this request is to move the imports to a dedicated code cell at the top or just to the first code cell (might contain other Python code) in the notebook.

Ah that's a good point. In practice, we usually have a dedicated cell for this yes, but I'm not sure if everyone works like that. Also, we sometimes put global configurations like logging levels or matplotlib styles in that top cell (example here).

Perhaps this could be configurable too? Difficult to think of good keywords here though, maybe imports-at-top-of-notebook = True and imports-at-top-of-notebook = "separate"? Well as I'm writing this, they already sound like a bad idea...

One could even consider implementing a a separate, additional rule that checks whether imports are in a dedicated cell.