Hello Gregor,
Am 22.12.23 um 00:04 schrieb Gregor Riepl:
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.
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.
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?
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.
I was able to fix not all of the current fallout, but quite a few of them.
--
Regards
Carsten
