That something vague is Armin's answer here: https://news.ycombinator.com/item?id=4207314
So I am essentially asking the same question. Armin's answer is mainly hand-waving: ''' TL;DR: you can't live without thread locals or you have a horrible API. Flask embraces them on every level and tells you how you can deal with the downsides of it. ''' Please support this statement. On Wednesday, 2 July 2014 12:56:58 UTC+10, avdd wrote: > > Despite searching the docs, this list, the stack(overflow|exchange) and > the googles I cannot find a satisfying explanation for Flask's > pseudo-globals, despite plenty of remarks and general wisdom that globals > and thread-locals are smelly. > > All the docs have to say is: > > ''' > Flask wants to make it quick and easy to write a traditional web > application. > '''' > > I remember once seeing something vague about making it easier to use > libraries, but without any supporting evidence. > > What are thespecific, concrete reasons Flask chose this (magic, implicit) > design over explicitness? > > -- You received this message because you are subscribed to the Google Groups "pocoo-libs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pocoo-libs. For more options, visit https://groups.google.com/d/optout.
