@Avasam Thank you for the issue and PR! Your fix looks good to me. I agree with changing Flake8 to version 3 or greater, as it doesn't look so likely that they will break their plugin interface on major releases. It's much more likely that I forget to update the versions, as happened this time...

Could you change the title of your commit to something more descriptive? When people are browsing the log, it won't be clear what was changed if the title is just "Fixes #2". Something like

Add flake8 v5 support

Fixes #2 

should be fine.

Sure thing. It was done quickly using the Github UI. I've amended the commit to a proper message.
Btw I don't currently have a poetry setup to update poetry.lock .

@rayjolt

Is this good to be merged?

@rayjolt Bump. Since this is one of my oldest still open PRs.
Alternatively I'd understand if you don't wanna maintain this plugin anymore, given the many other alternatives (namely

• https://docs.astral.sh/ruff/rules/unspecified-encoding/
• https://pylint.pycqa.org/en/latest/user_guide/messages/warning/unspecified-encoding.html
• https://flake8-encodings.readthedocs.io/en/latest/usage.html#flake8-codes

)
In which case you might wanna mark it as unmaintained / archived.