Is it time to retire the leoflexx plugin?

[Edward K. Ream]

#4465 reports that --gui=browser does not work with Python 3.14.

I have filed  flex issue #754 , but there is nothing else I can do.

Both LeoJS and LeoInteg are significantly more capable that --gui=browser, so it may make sense to remove the code (leoflexx.py) that supports  --gui=browser.

What do you think?

Edward

[Thomas Passin]

Looking at the Issues tab on the Flexx Github repo, there is this statement by the creator -

" Personally, I have moved on to other things and don't want to spent much time on Flexx anymore. I still find it an interesting project though, and I can try to find time to do some minimal maintenance or advice to e.g. keep adjusting to new Python versions."

This doesn't sound promising for keeping leoflexx working, does it?

[Edward K. Ream]

On Thu, Oct 23, 2025 at 10:11 PM Thomas Passin <tbp1...@gmail.com> wrote:

Looking at the Issues tab on the Flexx Github repo, there is this statement by the creator -

" Personally, I have moved on to other things and don't want to spent much time on Flexx anymore. I still find it an interesting project though, and I can try to find time to do some minimal maintenance or advice to e.g. keep adjusting to new Python versions."

Thanks, Thomas, for finding this. I missed it.

This doesn't sound promising for keeping leoflexx working, does it?

It's a mixed message. Adjusting to new Python versions is all we need now. But no, in the long term, we can't expect many improvements. To repeat my own opinion, leoflexx can't compete with Félix's various projects.

Edward