Publish new vesrion with flake8 v5 support.

[codeleta]

Rule request

Publish new vesrion with flake8 v5 support.

Thesis

You made flake8 v5 support.
Can you make a tag and publish it?

Reasoning

I want update flake8 and can't do this.

[sobolevn]

Sorry, but it does not work properly: #2511

[codeleta]

Oh I see. Thanks for answer.

[okainov]

+1 would really love to have new version with flake8 5.x support...

Seems like it was even implemented already in #2518

[okainov]

Any update on this @sobolevn ? More than a month has already passed, when do you expect creation of new release?

[sobolevn]

It still does not work. flake5 is broken, sorry.

[okainov]

@sobolevn thanks for clarification! But is there some open issue for the problem? Tried to briefly search, but didn't find anything really... Because from #2518 it looks like fully implemented and working (it wasn't reverted neither), could you please kindly point to what exactly is broken?

[sobolevn]

Here you go: https://github.com/PyCQA/flake8/issues?q=is%3Aissue+importlib+is%3Aclosed

[okainov]

Everything is closed there :) So I think everything is fixed?

[sobolevn]

Please, trying reading them: they are all closed as "won't fix".

[okainov]

Well, I did read them. The most discussed/making sense issue looks like this one PyCQA/flake8#1701. In the other repos the maintainers have also already updated saying the issue was fixed (see nils-braun/b2luigi#176; python/importlib_metadata#406)

And as flake8 maintainers indeed have mentioned, submitter does use (very) out-of-date flake8 version. And that's indeed "won't fix", one cannot argue with that. And the dependency on old importlib was also fixed by flake8 maintainer in PyCQA/flake8@aa002ee.

What I tried manually just to see what's happening is to run in clean Python 3.9 container pip install importlib_metadata (which installs 5.x) and then pip install flake8 (which doesn't install any importlib_metadata and installs flake8==5.0.4). Then running flake8 on some dummy files and it seemed fine, no crashes. And that's exactly why I'm asking - what is considered "broken" here? I'd be happy to submit (one more) issue to flake8, but I don't even see the issue, it looks working fine.

root@a7afcc18ba85:/# pip freeze
flake8==5.0.4
importlib-metadata==5.0.0
mccabe==0.7.0
pycodestyle==2.9.1
pyflakes==2.5.0
zipp==3.10.0
root@a7afcc18ba85:/# flake8 --version
5.0.4 (mccabe: 0.7.0, pycodestyle: 2.9.1, pyflakes: 2.5.0) CPython 3.9.15 on Linux

[okainov]

BTW flake8 6.x was recently released...

[dakotahorstman]

@okainov I'm running into this as well. Seems like @sobolevn either had something come up or he's just decided to stop maintaining the codebase. Considering his vague and unhelpful responses to you, I can't help but think the latter.

[dreamflasher]

@sobolevn What if @okainov or someone else would make a PR with flake8 v6 that passes all tests, would you accept that PR?

[dreamflasher]

Ping @sobolevn are you still working on wemake?

[okainov]

Okay, looks like this is becoming the second rapidjson with the maintainer @sobolevn being incredibly resistant to publish new releases for noone-knows-why reason. Seems like we need to find an alternative or just go away from using this tool as this problem explicitly blocks users of new versions.

[dreamflasher]

Idk what happened at rapidjson, but here it just looks like he's currently not working on the project anymore? I don't see any commits for the past 4 months. The big question is... will he ever be back?

And if he'll be back in a reasonable time, I would still think he'll update to new versions eventually. If he doesn't come back... is anybody stepping up to be the new maintainer? And sadly this means a hard fork likely, because I guess he won't give access to this repo?

[dreamflasher]

Welcome back @sobolevn :) Would you be open for a PR that passes all tests and provides Flake8 v6 compatability?

[positron96]

Just wanted to add that currently this project cannot be used with Flake8 VSCode plugin. The oldest version of plugin that can be installed (2022.6.0) requires flake8>=5.0.0

[Day0Dreamer]

@dreamflasher - Do you have a fork I can use?

I'm afraid the noone-knows-why reason, @okainov mentioned, won't go away for the duration of 2023.

I'm looking forward to keep using the updated version of this great tool. Got to keep the wheel turning

[dreamflasher]

I stopped using wemake. As @sobolevn is back and working on PRs, but not responding here/not working on this issue, I also doubt this will be resolved any time soon.
I'd appreciate a lot if you create a fork that works with current dependencies!

[Day0Dreamer]

@dreamflasher it would look like @sobolevn is plowing through the backlog. We've got to be patient. <3

[dolfinus]

Finally https://github.com/wemake-services/wemake-python-styleguide/releases/tag/0.18.0

[dreamflasher]

Thank you very much @sobolevn !