(sorry for the very late response, I only noticed your message just now)
I did come to the conclusion that Werkzeug 2.3.x has some bigger changes
that will break most of the existing packages in some way. The main
differences to Werkzeug 3.x than isn't that big.
Ok, that makes sense!
Although, I'm not 100% convinced that updating to 2.3 in the short run
to fix some currently broken packages, and then focusing on upgrading to
3.x isn't a better choice. 2.3 is also closer to 3.x, so that may make a
transition smoother.
Because a updated flask-login and other (updated) packages have also
underlying changes that require than a updated package of Werkzeug. And
some upstream projects did change their source in a way so they can deal
different versions of Werkzeug. So a usual update is magical fixing
build issues we did have in older versions against recent Flask/Werkzeug
versions.
Ok, now I get what mean. Thanks for the clarification and sorry for the
confusion.
