Flask 0.9 codename Campari released today

Edit: Why the downvote? I'm just fishing for anybody having newer info than what's on the website out of genuine interest and because HN tends to be a place where people would know; it's not meant as a troll.

uvtc• 14 years ago

I'm guessing that this section of the docs http://flask.pocoo.org/docs/advanced_foreword/#the-status-of... will get updated once the status changes.

sho_hn2• 14 years ago

Yep, I read that, and was e.g. wondering whether the upcoming 3.3 did anything to address the issues alluded to there.

Basically, it's a developing situation and it's not economical to change that text for every inch things move, but I'd love to hear what's in flight right now in this less formal context.

batista• 14 years ago

This very section is that worries me.

Nobody ever bothered updating it, not when the relevant WSGI spec came out, and not when Python 3.3 announced the byte str changes that would help.

If even Django and Pyramid can have a 3 roadmap --and even implementation--, surely Flask could too.

Seems like they just dont bother, so they put it in the backburner. Which is mighty fine, its a volunteer project after all, but I find said document misinforming, to say the least.

hoodoof3• 14 years ago

Python 2 is starting to smell very "legacy" and stuff that isn't moving to Python 3 is starting to look less relevant.

scott_w3• 14 years ago

Considering that some of the most common libraries aren't on Python 3, I'd hardly call Python 2 "legacy".

Until the libraries you need at least support Python 3, it's not worth even starting to move across.

amix2• 14 years ago

While Flask started as a joke I am happy to see it evolve! For me it's by far the most focused and polished framework for Python!

TazeTSchnitzel2• 14 years ago

One of the nicest things about Flask, for me, is there isn't any boilerplate. Unlike django, I don't need a script to produce a bunch of boilerplate code for me, just to create an app. I can type out some code, and run it. There isn't a "required" set of files.

Herald_MJ• 14 years ago

? web.py? Tornado? Any microframework?

ergo142• 14 years ago

Clearly you haven't tried Pyramid yet ;-)

heretohelp2• 14 years ago

I have, Flask is better. Pylons and Pyramid aren't that great.

bsg753• 14 years ago

Curious how Flask compares to Bottle, in terms of features, "developer velocity", performance?

falcolas3• 14 years ago

More features (such as the included Jinja2 templating system), similar developer velocity (built on the same principals and concepts), probably similar performance, since both rely on external http(s) servers to handle the heavy lifting.

The main advantage bottle holds over flask is that it's a single file that you can import, instead of a package. Makes it very portable.

bsg753• 14 years ago

As someone who is not a web developer, but has a need to create a few internal apps, portable sounds like simple - exactly what I need.

My desire: (1) grab data, (2) render chart / graph, (3) display in browser

Without needs like session management, concurrency, etc., Bottle "sounds" easier, which is mostly based on the 1 file import thing, and why I was looking at Bottle last time I did not get this project rolling.

antihero2• 14 years ago

How is that any easier than just using a virtualenv for anything but the most simple of scripts with zero other dependencies?

scorpion032• 14 years ago

Clearly this means 1.0 is around the corner. Any specific features, changes etc, that needs to be worked on, for 1.0?

SimonSapin• 14 years ago

I don’t see why 1.0 should necessarily follow 0.9. The whole point of having a dot in there is that we can make a 0.10.

That said, maybe 1.0 is around the corner. But I have not seen much more indication of that than after 0.7 or 0.8.

yashchandra• 14 years ago

3 cheers for Flask. I like how simple yet powerful this framework is. So far, I am loving it. Pretty soon looking to bootstrap one of my ideas using this framework.

bjornsing• 14 years ago

Slightly off topic but can't resist this little humorous spin on the Flask README:

> Flask [...] was developed with best intentions in mind.

And any bugs I guess is "the unintended consequences of good intentions...". :)

vph• 14 years ago

Well, the path to hell is paved with good intentions.

mfenniak• 14 years ago

Very nice. Almost painless upgrade here; had to make one change to my custom create_url_adapter to adjust for the possibility of request being None, but that was a minor change and documented to boot. Flask rocks.

Flask 0.9 codename Campari released today

Related Stories