flask

Agreed. There is an unofficial Python 3 port of Flask and Werkzeug, apparently[1]. And Armin says he started a “secret branch” a few months ago to explore adding Python 3 support[2], but no news since then. The sense I get from the essay[3] is that Python 3.0/3.1 were quite flawed, but that more recent minor versions have been moving in the right direction. I'll admit I haven't personally done much more with Python 3.x than kick the tires a bit. 1. https://github.com/puzzlet/flask 2. https://github.com/mitsuhiko/flask/issues/587 3. http://lucumr.pocoo.org/2011/12/7/thoughts-on-python3/

> I don't think pushing tweets to every user is a scalable approach. It would seem more sensible to read rather than push tweets associated with a user. I don't know about Twitter's infrastructure, but storing more than 1 copy of the same data wouldn't make that much sense. Suppose I have 5000 followers. How do you propose to get the timeline? Since you said "single copy of data", I assume you would do something like this: https://github.com/mitsuhiko/flask/blob/master/examples/mini... At twitter scale, that query will be a major bottleneck.

Flask is awesome and I'd strongly recommend it to anyone curious about doing webdev in python. When I was starting out, I found the source code to the Flask website itself really helpful for getting to grips with the basics: https://github.com/mitsuhiko/flask/tree/website/flask_websit...

For what it's worth, I implemented JSON based sessions for testing purposes: https://github.com/mitsuhiko/flask/commit/4df3bf2058954624f9... They are currently on a separate branch and they are known to break python-openid (and with that Flask-OpenID). I don't have a solution for that yet. If someone is really concerned regarding security you can copy/paste the code into your own project. The session interface in Flask is pluggable for a while already.

I haven't done the numbers in a while but from the given ratio I would assume your line checker tool treats docstrings as code. The red part there is for the most part just documentation, not code: https://github.com/mitsuhiko/flask/blob/master/flask/app.py (as an example)

Here's the source of Flask's `route` decorator: https://github.com/mitsuhiko/flask/blob/master/flask/app.py#... When you call `route` with a URL pattern, it returns an inner function which is used as the decorator. That decorator just records your route and function in the Flask URL map, and returns your function unchanged. So, Flask is arguably perpetuating a slight abuse of decorators, since it doesn't decorate or wrap your function at all, but merely saves a reference to it somewhere. But it's a fairly clean way to make up for the lack of code blocks or multi-statement anonymous functions in Python.

Actually, you'd probably want Express. var app = express.createServer(); app.get('/', function(req, res){ res.send('Hello World'); }); app.listen(3000); That is, admittedly, longer than PHP but it's arguably easier to understand what's going on, much easier to modify and extend, and just as easy to copy and paste off the web. For Sinatra: require 'sinatra' get '/' do "Hello World!" end Again, does PHP have any real advantage here? Python solutions will be similar. And in all those cases we can turn this into a full app with only a few more lines. Consider this example of a completely function blog: https://github.com/mitsuhiko/flask/tree/master/examples/flas... There's 76 sloc of code in the blog app, plus tests, templates, database access, and more. And it's clean, clear, and simple. What does the PHP equiva

Django[1] source is lovely, and they're pretty rigid about PEP rules, so it's a stellar example. Flask[2] source code is also lovely. [1] - https://github.com/django/django [2] - https://github.com/mitsuhiko/flask

> However, we've found reports of sendfile not working properly on certain platforms and we're still investigating, so I'm not convinced at this stage that the problem is with Flask itself. I am confused by your sendfile not working properly on certain platforms. If you set the X-Sendfile header, and the web server supports it, it should work fine. Flask send_file doesn't do much other than setting up the headers; and then either setting the X-Senfile header so that web server handles it, or sends it using WSGI file wrapper supports. https://github.com/mitsuhiko/flask/blob/master/flask/helpers...