I had the same problem. It is because Werkzeug 3.0.0 was released and Flask doesn’t specify the dependency correctly (requirements says Werkzeug>=2.2.0). This is why, Werkzeug 3.0.0 is still installed and Flask 2.2.2 isn’t made for Werkzeug 3.0.0. Solution: Just set a fix version for Werkzeug such as Werkzeug==2.2.2 in your requirements.txt and it should … Read more
You are missing the ProxyFix() middleware component. See the Flask Proxy Setups documentation. There is no need to subclass anything; simply add this middleware component to your WSGI stack: # Werkzeug 0.15 and newer from werkzeug.middleware.proxy_fix import ProxyFix from flask import Flask app = Flask(__name__) app.wsgi_app = ProxyFix(app.wsgi_app, x_proto=1) If you have Flask installed, you … Read more
People tend to overuse abort(), while in fact it is very simple to generate your own errors. You can write a function that generates custom errors easily, here is one that matches your JSON: def make_error(status_code, sub_code, message, action): response = jsonify({ ‘status’: status_code, ‘sub_code’: sub_code, ‘message’: message, ‘action’: action }) response.status_code = status_code return … Read more
Flask provides a test_client you can use in your tests: from source.api import app from unittest import TestCase class TestIntegrations(TestCase): def setUp(self): self.app = app.test_client() def test_thing(self): response = self.app.get(“https://stackoverflow.com/”) assert <make your assertion here> Flask Testing Docs
As of 0.10, Werkzeug doesn’t support OpenSSL contexts anymore. This decision was made because it is easier to support ssl.SSLContext across Python versions. Your option to re-write this code is this one: if __name__ == “__main__”: context = (‘cert.crt’, ‘key.key’) app.run(host=”0.0.0.0″, port=80, ssl_context=context, threaded=True, debug=True) See http://werkzeug.pocoo.org/docs/latest/serving/ for all possibilities.
Probably you were looking for Flask.before_first_request decorator, as in: @app.before_first_request def _run_on_start(a_string): print “doing something important with %s” % a_string
The workaround I use for now is to pin werkzeug to 2.1.2 in requirements.txt. This should only be done until the other libraries are compatible with the latest version of Werkzeug, at which point the pin should be updated. werkzeug==2.1.2
I had the same problem. It is because Werkzeug 3.0.0 was released and Flask doesn’t specify the dependency correctly (requirements says Werkzeug>=2.2.0). This is why, Werkzeug 3.0.0 is still installed and Flask 2.2.2 isn’t made for Werkzeug 3.0.0. Solution: Just set a fix version for Werkzeug such as Werkzeug==2.2.2 in your requirements.txt and it should … Read more
Werkzeug released v2.1.0 today, removing werkzeug.security.safe_str_cmp. You can probably resolve this issue by pinning Werkzeug~=2.0.0 in your requirements.txt file (or similar). pip install Werkzeug~=2.0.0 After that it is likely that you will also have an AttributeError related to the jinja package, so if you have it, also run: pip install jinja2~=3.0.3
I am running uwsgi version 1.9.5 and the option uwsgi –py-autoreload 1 works great