News for hackers. Stuff that matters.
Re:Advanced Flask Patterns by ch0wn on Friday July 06, 2012 @07:57AM (#4207355)
Thread locals are addressed in the docs:

    Yes it is usually not such a bright idea to use thread locals. They cause
    troubles for servers that are not based on the concept of threads and make
    large applications harder to maintain. However Flask is just not designed
    for large applications or asynchronous servers. Flask wants to make it quick
    and easy to write a traditional web application.

http://flask.pocoo.org/docs/design/#thread-locals
Re:Advanced Flask Patterns by brown9-2 on Friday July 06, 2012 @09:20AM (#4207570)
I haven't used Flask for a large application, but I'm curious why it would be bad for a large application - are there not enough features built in?

What would Python developers prefer to use for a large application - Django?

Re:Advanced Flask Patterns by chasingtheflow on Friday July 06, 2012 @01:49PM (#4208861)
Re:Advanced Flask Patterns by swah on Friday July 06, 2012 @08:43AM (#4207477)
I feel sad to read remarks like this one :)

If you have a large application, should you use what, Spring? If you use Spring, you'll have a large application.

Re:Advanced Flask Patterns by obiterdictum on Friday July 06, 2012 @08:03AM (#4207371)
It should be noted that thread locals play well with greenlets, so it works well with gevent-style asynchronous servers.
Re:Advanced Flask Patterns by the_mitsuhiko on Friday July 06, 2012 @08:31AM (#4207442)
We have builtin support for greenlet concurrency even without monkey patching I should add :-)
Re:Advanced Flask Patterns by irrationalidiom on Friday July 06, 2012 @12:30PM (#4208449)
I want to thank the flask team for this. we are using flask + gevent in production and it has been highly performant (1200 requests a second for our app) and stable :-)
Re:Advanced Flask Patterns by balac on Friday July 06, 2012 @06:03PM (#4209854)
Are you running that on a single server? Care to share the specs?