use python 3.12 in build action

[FoamyGuy]

This resolves an issue that I'm facing during the docs build for a new library: https://github.com/adafruit/Adafruit_CircuitPython_Argv_File/actions/runs/14862174307/job/41729654249#step:2:1072

I'm not entirely certain the root cause of the issue but it seems that something inside of python 3.11 is unappy trying to parse the line of code return f"{file_location}.{path.absolute().replace("/", "_")}.argv"

The line of code works fine on a CircuitPython device, I tested inside of local containers and on python 3.12 and 3.13 the docs do build successfully. They got built successfully inside of RTD as well which uses 3.13. The issue building seems to be specifically inside github build action where it uses python 3.11.

[tannewt]

Fine with me. Thanks!

[FoamyGuy]

I didn't realize it at the time because I was working on newly cookie-cut libraries with ruff, but this change actually breaks our non-ruff library pre-commit runs because pylint versions < 3.0 are unsupported on python 3.12 and we use 2.17.4 currently.

I am thinking the easiest path is to adabot patch all repos that still use pylint to update them to use pylint v3, while we continue working to migrate them to ruff. But if we wanted instead we could take a more "rip the bandaid" approach and take the opportunity to just swap the remaining pylint ones to ruff.

[tannewt]

I didn't realize it at the time because I was working on newly cookie-cut libraries with ruff, but this change actually breaks our non-ruff library pre-commit runs because pylint versions < 3.0 are unsupported on python 3.12 and we use 2.17.4 currently.

I am thinking the easiest path is to adabot patch all repos that still use pylint to update them to use pylint v3, while we continue working to migrate them to ruff. But if we wanted instead we could take a more "rip the bandaid" approach and take the opportunity to just swap the remaining pylint ones to ruff.

Any idea how many we've switched to ruff and have remaining?

[FoamyGuy]

I do not know for sure. I would guess maybe 20-25% are on ruff and the remaining need moved still.

We discussed this a bit in the internal meeting and decided to work on switching them to ruff. I'm going to use the opportunity to get claude code setup locally in a container and get practice using it that way instead of the web UI. Hopefully it can smooth some of the tediousness of swapping, removing pylint disable comments, and updating code that gets flagged by ruff.

[tannewt]

I do not know for sure. I would guess maybe 20-25% are on ruff and the remaining need moved still.

We discussed this a bit in the internal meeting and decided to work on switching them to ruff. I'm going to use the opportunity to get claude code setup locally in a container and get practice using it that way instead of the web UI. Hopefully it can smooth some of the tediousness of swapping, removing pylint disable comments, and updating code that gets flagged by ruff.

Perfect! That sounds like a great use of claude code. It loves fixing lint errors.