Thank you very much for the detailed explaination.
Yes, the patch of flake8 and pyflakes which I submitted
yesterday would break py-python-lsp-server.
Please hold the patch.
Thank you !
wen
________________________________________
发件人: Daniel Dickman <didick...@gmail.com>
发送时间: 2024年1月10日 7:07
收件人: wen heping
抄送: ports@openbsd.org
主题: Re: devel/flake8: Update to 7.0.0
On Tue, 9 Jan 2024, wen heping wrote:
> Hi, ports@:
>
> Here is a simple patch for devel/flake8 to update to 7.0.0.
> It build and run well on amd64-current system.
>
> Cheers !
> wen
Hi Wen, thank you for the proposal!
Unfortunately see devel/py-python-lsp-server which has:
RUN_DEPENDS = devel/flake8>=6.1.0,<7
So this means that unless something else changes we cannot go to flake8
without breaking spyder at the moment. I haven't checked if there's an
update of python-lsp-server which solves this.
Also the other reverse consumers don't say explicitly what versions they'd
need, but they would be good to check if you didn't already.
In general it would be a good idea to check reverse consumers when
submitting port updates as updating the port itself is not a sufficient
test before committing.
p.s. if you do plan to work on any of the Python code checkers and linters
like flake8, black, etc, etc. Then you should definitely look at the
entire spyder and jupyter ecosystems as those tend to have tight version
dependencies on the code checkers.
Now spyder is already updated to the most current version so what's in the
tree is ok to check. For jupyter I have a working update, but not to the
latest yet.
For guidance, my plan is to update jupyter in the next update so that
these are the new version upper bounds:
- jupyter-notebook < 7
- jupyterlab < 4
- jupter_server < 2
Hope that helps your porting efforts.
