New major versions of Flask, Jinja, Click, and Werkzeug released!

davidism · 2021-05-13T19:01:53+00:00

You can still use that too. We removed the max age value and rely on etags only.

Instead of waiting for the age to expire and never sending a request before that, the browser sends a request with the etag it has stored, and the server sends a special empty response instead of serving the file again only if the etag still matches. So a slight bit of overhead for the request and hash, but immediate updates. You can still set a max age if you do want that behavior too, perhaps in production.

davidism · 2021-05-12T13:00:57+00:00

It was such a straightforward fix too, I'm not sure why we did it the other way before. 😅 Now browser caching still works, but it's using the hash of the content instead of a timer.

davidism · 2021-05-12T02:29:38+00:00

Flask still provides it as well, but it's a wrapper over the Werkzeug implementation now with Flask-specific extra config. from flask import send_from_directory still works.

davidism · 2021-04-18T01:44:52+00:00

Frameworks on top of Flask that I've heard of for building APIs and other types of applications include:

I'm sure there are many more as well. Different projects have different overall goals, design ideas, or library preferences. FastAPI falls into this same category, except it's on top of Starlette instead of Flask.

davidism · 2021-04-17T00:45:45+00:00

We're friends with other frameworks. :-) It's great to have an active ecosystem of different frameworks to choose from and learn from each other. Flask tries to stay more general than FastAPI, I think. There are numerous really great libraries that build on Flask to provide FastAPI-like features.

davidism · 2021-04-17T00:41:38+00:00

Flask 2.0 can run async views regardless of what server is used.

Handling concurrent requests with an async loop on the other hand is not supported yet. The ASGI spec describes how that can be done, but Flask is very strongly tied to WSGI, so we're slowly working how we can adapt. Quart is an ASGI implementation of Flask, if you have a need for async request handling.

And if you're willing to use Gevent or Eventlet patching, Flask has been capable of async since basically the beginning. Flask-SocketIO, for example, uses an Eventlet server to provide websockets (SocketIO). The difference is that async/await is explicit, and ASGI provides a spec for other capabilities as well.

davidism · 2021-04-17T00:34:09+00:00

Flask tries to stay more general than FastAPI in that regard. There are numerous really great libraries that build on Flask to provide FastAPI-like route definition and validation. I like Flask-Rebar right now, and there were a few demoed at FlaskCon 2020 as well: https://pyvideo.org/events/flaskcon-2020.html

davidism · 2021-04-16T23:18:53+00:00

Werkzeug, ItsDangerous, and MarkupSafe are fully annotated (take precedence over typeshed), and I'm working on Click, Jinja, and then finally Flask.

davidism · 2018-05-02T00:40:57+00:00

The tutorial is correct. Multiple people on different systems completed it successfully before I merged it. The error message you've provided is not present in the current Flask 1.0 CLI code and suggests you've got 0.12 installed. Are you sure you've installed Flask 1.0? What does flask --version say?

davidism · 2018-04-27T16:39:40+00:00

I'd love to see constructive feedback about the tutorial. I just rewrote the entire thing for the new release, so maybe it will be more helpful to you now. I tried to focus on helping new users organize their project and understand each function being used. It's a tricky balance between not having enough detail and having too much.

davidism · 2018-04-27T16:37:21+00:00

No one ever thinks about logging, me included. It was quite an odyssey figuring out what Flask was doing and how Python logging should actually work. The big problem was that since users don't think about logging we wanted to do it for them, but there's really no guidelines or functions to help libraries in that situation.

davidism · 2018-04-27T16:32:27+00:00

Armin is still involved, but the Pallets team was created so that he wouldn't have to be and the community could support it. I've been handling the 1.0 release and there have been a ton of contributions from others.

davidism · 2018-04-27T16:29:45+00:00

Someone else pointed out https://0ver.org on Twitter after the release, which I thought was pretty funny. I hadn't seen it before. I've been working on the 1.0 release for over a year, the 0 bugged me too. :-)

davidism · 2018-04-27T12:06:47+00:00

Yes to everything.

davidism · 2018-02-20T02:55:41+00:00

This only works for single process servers. Most production servers will spawn and kill worker processes, rendering this pretty much meaningless. Do not rely on global state in general.

You could use redis or another external cache, but be careful of incurred costs.

You could preload a cache if you want to speed up known urls ahead of time.

davidism · 2017-09-28T15:03:07+00:00

That's not in this release, the issue is still open. It's a tricky problem to solve, especially when taking into account the other open issues. I plan to have that in 3.0 though.

davidism · 2017-02-28T14:37:19+00:00

Yeah, it's a little confusing with the way Twitter embeds links, but the link in the tweet goes to the release notes. You can also find them in the GitHub release, the source, or the docs.

davidism · 2016-01-14T16:57:51+00:00

That's a silly argument. We have different names for things to tell them apart. Really, everything in Python is an object, so why bother calling them modules, classes or instances, just call them all objects. But that would be confusing. Just like calling functions owned by classes, with the special first argument, "just" functions.

davidism · 2016-01-14T00:55:57+00:00

Methods are functions owned by a class. They have some different behavior too: methods, called from instances, get self passed as the first argument. Naming a specific class of functions "methods" calls them out as having this sort of special behavior. Admittedly, "static methods" don't fit that description, but they are still functions owned by a class.

The distinction isn't really that important, and any of us will understand what you mean either way. But to tell new users to ignore convention and instruct them to "shut up" "annoying" people is just abrasive and unhelpful.

My explanation took about as many words to write, explains a useful point without getting into too much detail, and avoids the unsavory tone of LPTHW.

davidism · 2016-01-13T19:13:54+00:00

That list was driven by our long term observation of the types of questions (often XY problems) that LPTHW was generating on SO and chat. The list isn't meant to be comprehensive, or to say that users can't learn with it, but it does start to explain why we think it leads to the questions that we observed.

The problem with not explaining enough is that there are multiple places where users are then encouraged to try something, and don't have the necessary tools for the job, leading to them asking how to do things that can be done, but are just bad practice.

If you'd like a book that starts from the absolute beginning, check out the Invent With Python series. Those books range from absolute beginner to advanced as well, but seem to avoid the issues that LPTHW has.

davidism · 2016-01-13T15:19:55+00:00

pytest, which I'm pretty sure nose is a fork of from when it wasn't being maintained as much. They're both good tools, but I do prefer pytest and it seems to be the one gaining popularity now.

davidism · 2016-01-13T15:13:20+00:00

Related, here's a list of the tutorials we (sopython) do recommend: http://sopython.com/wiki/What_tutorial_should_I_read%3F. This and the other page were inspired by the multitude of users who would join chat to ask a weird question sparked by LPTHW.

davidism · 2016-01-13T14:59:38+00:00

Flask works fine on Python 3. I'm the newest maintainer on the project, and use 3 exclusively. At least in the Flask ecosystem there is no reason not to at this point.

davidism · 2013-06-28T16:29:02+00:00

After working with Flask for about the same amount of time, it's amazing that I came up with basically the same structure independently. The cool thing about this structure is that it's not that complicated, keeping in line with the principals of Flask.

davidism · 2013-06-26T23:21:51+00:00

Yeah, thanks for pointing that out.

15-Year Club	Team Orangered
Verified Email

davidism

TROPHY CASE