Python 3 released on '08. Flask debuted a couple of years later in 2010, on Python 2. 11.5 years later Python 2 is nearly in the rearview. The history of the Python 3 release is surely an impressive one.
On a more related note, props to devs/contributors for this release. My experience with Flask was pop-up projects and never mission critical, but i always found it a joy to use and quite intuitive.
Flask is a great library which gets out of your way - I find it a joy to use compared to Django.
Although there are some dark sides, particularly with how Flask interacts with Werkzeug during exceptions when you need CORS (for example, we can't overwrite exception page's Access-Control-Allow-Origin headers with @app.after_request since these headers are set by Werkzeug and can't be overwritten in Flask).
This prevents us from levering Flask's default except handler in certain environments which require custom headers for exception handling page.
Agreed. I found Flask after being really annoyed with learning Django. Flask + Heroku is an awesome combo for the hobbyist like myself.
But this works for me:
@app.errorhandler(ApplicationError)
def handle(e):
resp = e.args[0]
resp.headers["Access-Control-Allow-Origin"] = "..."
resp.status_code = 500
return resp
@app.route("/err")
def err():
raise ApplicationError(jsonify({"reason": "test"}))I was talking about using werkzeug's builtin exception handler but with custom headers - which doesn't appear to be supported.