pagure

#4739 Support werkzeug 1.0 which changed some of its top-level imports
Merged by pingou. Opened by pingou.
fix_werkzeug  into  master

Download 4739.patch

What used to be accessible as werkzeug.secure_filename now is
accessible only as werkzeug.utils.secure_filename.

Signed-off-by: Pierre-Yves Chibon pingou@pingoured.fr

rebased onto 78427e8d3250ee865a53c5d67148809fadf00554

An actual fix looks much better than my lock_until_fix_arrives thing :D

Let see if jenkins is happy with it =)

if jenkins:
   :thumbsup:

:thumbsup:

Ah, I was hitting a similar issue when trying to run pagure and the test suite in vagrant.

werkzeug.url_encode is now only availabe at werkzeug.urls.url_encode (but this error happened in flask_wtf, not in pagure code itself).

@decathorpe odd that we aren't facing this issue in our test suite.

Anyway, jenkins is happy so let's get this in! :)

Pull-Request has been merged by pingou

last time I fixed vagrant, I tried to mimic the same pip venv that we have on pip container, but we are running tox with python35 and flask100 constraints on the test suite while vagrant does not have those constraints tu build the venv (just --site-packages I think)

So the difference could be there
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.