Hi Carsten,
I can see that 3.0.1 is currently in experimental, but it would be enough to
upgrade to the latest 2.x to fix this issue.
this makes not really sense to me. Flask 3.0.0 and Werkzeug 3.0.0 was
released on 09-30-2023, so almost three months before. Putting energy
into Flask 2.3.5 and fix other related packages while 3.x is on the way
is a waste of time in my eyes as we would need to work at least twice on
some packages...
Absolutely!
My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit
for release, it should be enough to upgrade to 2.3.5 to address these
unit test failures.
flask-login got recent updates which so far I've seen will fix these
issues in the test suite. So if you want to push things further try to
update/patch flask-login to a recent version targeting experimental.
Just rebuilding flask-login against the version of python3-werkzeug in
experimental will not fix the problems, so also not an intermediate
update to 2.3.5, Python 3.12 is now very strict about deprecation
warnings.
That doesn't make any sense to me. These deprecations are obviously in
werkzeug and not flask-login. Why would changes in flask-login fix them?
Not saying flask-login shouldn't be updated, but that's not the right
scope for this bug report.
Regards,
Gregor
