fix HTML display of Spectrum objects

[drammock]

closes #13025

[drammock]

OK doc build finally works as expected: https://output.circle-artifacts.com/output/job/d15fc82a-e80e-4e7d-97b1-9f5deb544fce/artifacts/0/html/auto_tutorials/time-freq/10_spectrum_class.html
previously it was not erroring out but some of the _repr_html_() calls were failing, so the tables were only getting displayed for EpochsSpectrum, not for Spectrum objects.

In worse news, there are very weird things going on with pre-commit. We're running it in 3 places:

• pre-commit.ci
• azure (

  mne-python/azure-pipelines.yml

  Line 60 in 05bd738

  make pre-commit

  )
• GH action (

  mne-python/.github/workflows/tests.yml

  Line 26 in 05bd738

  - uses: pre-commit/[email protected]

  )

In this PR the hook was failing on azure because it wanted to change the README min dependency list from Python 3.9 to 3.10. that is a correct change because our README and pyproject.toml are out of sync with each other.

When I proactively changed the readme from 3.9 to 3.10 in 13b06a3, the local run of the dependency-sync hook was skipped, and now it succeeds on azure, but fails on GH Action (it wants to change it back from 3.10 to 3.9). I cannot figure out why.

Note that the dependency-sync action is not run on pre-commit.ci because it's excluded by the ci: skip: section of the config (which is ignored by azure/GHA).

I'm scratching my head as to why we run precommit in 3 places, and not sure what to do to address this, other than remove the GHA run because (1) it's behaving weirdly and (2) it uses a dispreferred, maintenance-only precursor to precommit-ci.

[larsoner]

I'm scratching my head as to why we run precommit in 3 places

I think the argument was to save some CI resources given that people will have to fix things

and not sure what to do to address this, other than remove the GHA run because (1) it's behaving weirdly and (2) it uses a dispreferred, maintenance-only precursor to precommit-ci.

Fixed and future-proofed by https://github.com/mne-tools/mne-python/pull/13040/files#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9R81 . So we can revert the removal (or not) here, up to you.

[drammock]

we can revert the removal

Ok with me. Feel free to do it if you're at an actual computer (not phone). Otherwise I'll get to it next week maybe