You might want to include how Flask utilizes Werkzeug for its WSGI application. Flask is the "glue" between Werkzeug, the request, Jinja2, and other extensions. As per the palletsproject.org site, "Flask wraps Werkzeug, using it to handle the details of WSGI while providing more structure and patterns for defining powerful applications." ref: palletsprojects.com/p/werkzeug/
n/p I really liked your post. I don't think there is enough discussion about this topic for those that are learning how to build web applications with Flask (or any python web framework). I think it's difficult for beginners to grasp what exactly is going on at this level. If you wanted to take it further you could go a little more in-depth and discuss routing and the various HTTP verbs. Either way, this is a good reference.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You might want to include how Flask utilizes Werkzeug for its WSGI application. Flask is the "glue" between Werkzeug, the request, Jinja2, and other extensions. As per the palletsproject.org site, "Flask wraps Werkzeug, using it to handle the details of WSGI while providing more structure and patterns for defining powerful applications." ref: palletsprojects.com/p/werkzeug/
Great point! Updated post to include mention of Werkzeug library. Thanks for pointing out!
n/p I really liked your post. I don't think there is enough discussion about this topic for those that are learning how to build web applications with Flask (or any python web framework). I think it's difficult for beginners to grasp what exactly is going on at this level. If you wanted to take it further you could go a little more in-depth and discuss routing and the various HTTP verbs. Either way, this is a good reference.