Add notes from the 2022-11 meeting

[encukou]

I missed most of the meeting, so I'm mostly just copying the document here.

[CAM-Gerlach]

A few minor comments, otherwise LGTM

[CAM-Gerlach]

As for the build warning due to Sphinx using the deprecated imghdr module in Python 3.11,, @AA-Turner I thought I remembered you folks already fixing this in 5.x, or am I confused?

[hugovk]

Sphinx is failing on the CI because we're turning warnings into errors (-W error) and Sphinx is using imghdr, and triggering a deprecation warning:

Run python -bb -X dev -W error -m sphinx --color -n -E -a -W --keep-going docs build
Running Sphinx v5.3.0

Exception occurred:
  File "/opt/hostedtoolcache/Python/3.11.0/x64/lib/python3.11/warnings.py", line 514, in _deprecated
    warn(msg, DeprecationWarning, stacklevel=3)
DeprecationWarning: 'imghdr' is deprecated and slated for removal in Python 3.13
The full traceback has been saved in /tmp/sphinx-err-tfj_[8](https://github.com/hugovk/docs-community/actions/runs/3445416680/jobs/5749102789#step:5:9)37y.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!

With pytest, you can disable arbitrary warnings, but looks like Sphinx can only suppress certain ones - is that correct @AA-Turner?

Options to fix:

• Wait for Sphinx to fix imghdr is deprecated and slated for removal in Python 3.13 sphinx-doc/sphinx#10440 and release
• Downgrade from Python 3.11 to 3.10 to avoid the deprecation warning (until it's fixed)
• Don't turn warnings into errors (until it's fixed)

[AA-Turner]

This is unfortunate.

Would adding -W ignore::DeprecationWarning:imghdr after the current -W error call work?

A

[hugovk]

Nope: hugovk@0e078fb

https://github.com/hugovk/docs-community/actions/runs/3445670511/jobs/5749653832

[CAM-Gerlach]

Yeah, as mentioned I thought that was already fixed upstream since IIRC we saw it on the PEPs once we started testing on 3.11 (but it didn't block, since we didn't run with python -W error or sphinx -W yet), but it seems not.

Nope: hugovk@0e078fb

Did you try just -W ignore::DeprecationWarning? It looks like the stacklevel might be wrong on the warning so it could be coming from warning rather than imghdr, and I've had issues with modules not matching when they should from the CLI.

If that doesn't work,

Downgrade from Python 3.11 to 3.10 to avoid the deprecation warning (until it's fixed)

is the least bad option, IMO, since it avoids silencing any valid warnings and there isn't a strong pressing need to ensure this runs on 3.11, since AFAIK unlike e.g. the PEPs it doesn't have its own custom theme and Sphinx extensions.

[hugovk]

Did you try just -W ignore::DeprecationWarning? It looks like the stacklevel might be wrong on the warning so it could be coming from warning rather than imghdr, and I've had issues with modules not matching when they should from the CLI.

Bingo! Please see PR #69.