Why does flask-jwt-extended v3.25.1 (latest 3.x version) require Flask<2?

[boompig]

It doesn't seem that there is any conflict with (for example) Flask 2.0.1, so why is this an enforced dependency? Is there some particular feature of Flask v2 that breaks Flask-JWT-extended?

Version 4 has many breaking changes so the upgrade path is a little difficult. It would be nice if I could continue to use 3.x for a little longer with at least Flask 2.0.1.

[vimalloc]

flask-jwt-extended v3 required Flask < 2 because it was released 18 months ago, which was a few months before flask flask v2 was released. I don't remember what all incompatibility changes has happened between then and know, but I do think there have been a few.

At the end of the day, I think the biggest thing is that I don't think the energy I would have to put in to maintain the v3 branch of flask-jwt-extended is worth it. A lot has changed over the past 18 months, from the code itself, to the infrastructure around the code (CI, deploy tools, etc), and having to figure all that out on top of insuring flask version compatibility is more work then I can put in for a very old release. It also opens the door for me having to continue maintaining the v3 branch for the foreseeable future which is not something I want to do.

I'm sorry, I know that isn't helpful for the particular issue you are facing, but I just don't think that is work I can justify taking on. I would be more then happy to help with any issues that might arise going from the v3 to the v4 release though!