3 ms·
IMO this is the composition vs inheritence debate. In the Python world, WSGI was really a break-through idea (a decade ago!) - parse the request up front and p
by lifeisstillgood 14y ago
IMO this is the composition vs inheritence debate.
In the Python world, WSGI was really a break-through idea (a decade ago!) - parse the request up front and pass the text down a chain of functions each of which can modify the request / response.
That way the chain you build is the chain used.
Every python web server uses it behind the scenes, and then
tries to make bits of it "easier" for you by hiding the underlying goodness.
Its usually a good trade off, but it kind of takes away the point.
So, I would say, (python) learn how to deploy your own WSGI app on gunicorn behind Nginx. And put security in using repoze.who.
Then you can choose to replace your app with Flask. Or django. Or ...
build up from the ground