Address linting and test errors

[tsalo]

Apologies for the unsolicited PR. I mostly just wanted to see why tests were failing in the last commit, but the logs were expired.

[paquiteau]

Hi, no worries, Any help is welcome!

[tsalo]

It looks like the linter-check job runs black, but style issues flagged by that step don't affect the job's status? I.e., it's passing now, but if I navigate to the Black Check step in the CI log there are a bunch of things black would change.

[Remi-Gau]

@tsalo: aren't you afraid that adding the word typo in the title of the PR may summon the codespell demon? (AKA @yarikoptic) 😜

[tsalo]

oohhh good point! 😄 Plus this is mostly about getting the linter and tests passing at this point anyway

[Remi-Gau]

yay: all green !

[paquiteau]

Thank you for the clean up! I guess we have a good starting point to built upon :)

[tsalo]

Weird... CI is failing on master. https://github.com/paquiteau/patch-denoising/actions/runs/11163580095/job/31030882890

Also the docs build needs to be fixed.

[Remi-Gau]

is that a flaky test ?

[Remi-Gau]

I can reliably get it locally.

[Remi-Gau]

weird: the fail happens on #7 on python 3.8 but not on #6 that does not run 3.8 but I get the fail locally with python 3.12...

[Remi-Gau]

OK my bad: when running locally in proper virtual environment (and not my usual conda 'ecosystem' - larger and meaner than an environment), everything is OK.

So I would try merging #6 to stop supporting py3.8 and get rid of the error.

[tsalo]

Sounds good to me!

[yarikoptic]

@tsalo: aren't you afraid that adding the word typo in the title of the PR may summon the codespell demon? (AKA @yarikoptic) 😜

• Add codespell support (config, workflow to detect/not fix) and make it fix few typos #12