Flask 2.0.0 has been merged into master

Post by avinassh » Wed, May 12, 2021, 9:00 AM UTC

postpawl wrote: post #15

dheera wrote: post #6

Earlier quoted context omitted.

I've moved most of my Flask projects to Express and NodeJS. Flask was just a PITA to deploy properly in a way that it could handle lots of concurrent connections without a massive memory footprint, and async in Python is a mess. The JS ecosystem has on the other hand moved to async and Promises as the standand/default way to implement things, which makes things much easier. Express middleware is also just easier to w…

You looked into using gevent workers? Sometimes you need to make tweaks to C-based dependencies to make them not block the event loop, but it should work fine for doing a lot of concurrency without a bunch of rewriting. Usually your bottleneck is your database anyway.

Post by mvolfik » Wed, May 12, 2021, 9:42 AM UTC

rastapasta42 wrote: post #31

liquidise wrote: post #8

> Drop support for Python 2 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 i…

You would be surprised by the amount of mission-critical code which runs on Flask. 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…

    @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"}))

Post by rastapasta42 » Wed, May 12, 2021, 1:13 PM UTC

mvolfik wrote: post #44

rastapasta42 wrote: post #31

Earlier quoted context omitted.

You would be surprised by the amount of mission-critical code which runs on Flask. 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…

How are these set in werkzeug? Sound like you would be using the werkzeug dev server then... 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"}))

Post by dayjah » Wed, May 12, 2021, 4:05 PM UTC

heavyset_go wrote: post #39

dheera wrote: post #32

Earlier quoted context omitted.

The main problem is that many Python libraries come in only sync flavor and using them together with asyncio is a pain. NodeJS libraries are almost all standardized to async now. Hell, even Tensorflow.js can give you Promises of computation results.

Seems pretty painless to me: $ python3 -m asyncio >>> from requests import get >>> url = 'https://example.com' >>> response = await asyncio.to_thread(get, url) A lot of Python libraries now offer async APIs, have async support on their short term roadmaps, or other async projects have replaced them.

Post by systemvoltage » Wed, May 12, 2021, 4:13 PM UTC

Hasnep wrote: post #43

systemvoltage wrote: post #40

> Add route decorators for common HTTP methods. For example, @app.post("/login") is a shortcut for @app.route("/login", methods=["POST"]). #3907 Why? By default, it’s GET if you don’t specify a method. But now with this change, for special routes such as “/login” it’s POST. IMO these kinds of things make for “gotcha” moments. Just keep defaults simple without special exceptions.

I think you've misread the change, it's nothing to do with login being a special case, it's about moving the HTTP method from the methods argument to the function name.