9 ms·
New Werkzeug and Flask Releases
- manuletroll 13y agoPython 3 support! Now I can make the switch. Congratulations to Armin and all contributors, and a big thank you!
- landypro 13y agoThe Flask docs have a small write-up on the things to look out for before jumping ship to Python 3. http://flask.pocoo.org/docs/python3/ http://flask.pocoo.org/docs/python3/
- fyolnish 13y agoI clicked this expecting a new release from Farbrausch : /
- dualogy 13y agoUnlikely, right? Also their stuff uses double-k, so it's werkkzeug IIRC..
- corford 13y agoCongrats & well done guys :) Flask was the last major block preventing me from seriously moving over to Python3 so I guess that means it's time to begin porting! (there goes my weekend...)
- bjourne 13y agoFlask is about the most beautiful Python code you can write. Check out any other Python framework and they may have a decent api, but on the inside it is messy and confusing. Reading Flask source code on the other hand is a joy. There's no crazy stuff and few convoluted pieces + lots of comments so it is really easy to hack something if you must. Any Python coder who wants to improve their game definitely should study Flask because it is such a great piece of software engineering.
- calpaterson 13y agoFor what it's worth, the internals of Bottle are very clean (and extremely simple - the entire library/framework is just one file).
- the_mitsuhiko 13y agoI know I'm biased on that, but if the internals of Bottle are clean it's doing something wrong :) WSGI/HTTP are incredible complex and in fact, too complex to fit into a single Python file. There is a good reason for why Werkzeug (which Flask is based on) is 15000 lines of code.
- aptwebapps 13y agoIt's in a single file which happens to be a little under 3500 lines long ...
- habitue 13y agoRight, he's implying that the implementation is not as complete, or is incorrect because the problem space is more complex than that.
- aptwebapps 13y agoI doubt he or she was aware it was 3500 lines long. While not the same as 15000, it isn't all that far off.
- schleppy_oc 13y agoI am pretty certain that he, the_mitsuhiko (aka. Armin Ronacher), being the main developer behind Werkzeug and Flask knows exactly how long bottle.py is.
- aptwebapps 13y ago
- clicks 13y agoTerrific news! Many thanks to all who made it possible. https://python3wos.appspot.com/ https://python3wos.appspot.com/ needs an update. :)
- jdboyd 13y agoThat will update once the author of flask updates its pypi entry.
- galaktor 13y agoHere I was thinking this was about "werkkzeug" by Farbrausch
- sigzero 13y agoThis is awesome. Been waiting to use it!
- taude 13y agoTime to update some extensions!
- drawkbox 13y agoFlask is a very solid python microframework and a joy to work with. So nice it is on Python 3 (3.3+) now. boto is the only thing needed for full on Python 3 here.
- kryten 13y agoI picked up flask for a one off helpdesk request frontend for someone a few months ago. Compared to asp.net, its an absolute joy to work with. It makes me not want to grind my face off with a blunt spoon :) Glad to see some awesome progress with it.
- danibx 13y agoI read somewhere that Flask was born as an Aprils first joke. So I ask. How safe is it to use in a real project? Is it a serious project today? Would you recommend Flask to someone who has never done any server side programming?
- alexk 13y agoYes, it's pretty reliable. We (mailgun.com) use it in production, our deployment handles thousands of requests/sec, we have not seen any flask-related issues so far in 2+ years. You can use pool of flask + twisted powered services behind nginxes: Nginx ---upstream pool--> twisted.wsgi + thread pool + flask app Something like that: https://gist.github.com/klizhentas/5775158 https://gist.github.com/klizhentas/5775158
- dkh 13y agoRegardless of Flask's humble beginnings, it is indeed a serious project, very stable, and quite awesome. And yes, I would recommend it for your use, assuming you want to learn Python as a whole. Flask is easy enough that you can start building an app right away, but at the same time, it leaves out all the extra 'magic' that ship with things like Django, so you'll be learning a lot more Python as you add onto your app. It's a great mix of simplicity and power, and is great for learning. Go for it.
- huxley 13y agoI'm curious about what you think is "magic" in Django? It does have a lot more included than Flask/Werkzeug/Jinja2 but it did start in the era before Pip/VirtualEnv existed so a lot more had to be included. After numerous purges (the magic-removal-branch being the biggest) and deprecations over the years since 1.0, Django is IMO pretty magic-free. If you have suggestions of what isn't Pythonic enough, I think the core team would appreciate a ticket on Trac: https://code.djangoproject.com/newticket
- Funnnny 13y agoI think it's the different between a normal python application and a web app: url dispatcher/route, request handler, template, extension...I started with Django, but Flask clears thing better for me.
- chris_mahan 13y agohttp://werkzeug.pocoo.org/download http://werkzeug.pocoo.org/download 404
- joeyespo 13y agoThis was changed to https://pypi.python.org/pypi/Werkzeug https://pypi.python.org/pypi/Werkzeug See https://github.com/mitsuhiko/werkzeug/commit/6e74b5be39d2409a9e7f9d1a6e2bafef729c863b https://github.com/mitsuhiko/werkzeug/commit/6e74b5be39d2409...
- chris_mahan 13y agoThe "Download page" link in http://werkzeug.pocoo.org/docs/installation/ http://werkzeug.pocoo.org/docs/installation/ needs to be fixed then! (From the tarball release Download the most recent tarball from the download page.)
- cstuder 13y agoSo we're a PHP shop thinking about moving to Python. With this release, can we immediately start using version 3? The Flask page still recommends holding back... (http://flask.pocoo.org/docs/python3/ http://flask.pocoo.org/docs/python3/)
- irahul 13y ago> With this release, can we immediately start using version 3? You should stick with 2.7 As mentioned in your linked blog post, porting Flask to Python 3 wasn't the issue. The issue is the other libraries which you will use to build your web application which aren't on Python 3 yet. You can try to build a unified code base(runs on both 2.7 and 3) http://lucumr.pocoo.org/2013/5/21/porting-to-python-3-redux/ http://lucumr.pocoo.org/2013/5/21/porting-to-python-3-redux/
- corford 13y agoLike irahul has said, the issue is the Flask extension ecosystem and documentation lag rather than Flask itself. Which basically means YMMV depending on what you need to get done :) If you are writing most of your own code and not using Flask extensions then you could well be fine (unless, like the linked post says, you discover a few months down the line you _do_ need a couple of extensions and they haven't been ported yet!). Also worth pointing out that lots of other great python libraries now fully support python3 so you can get a lot done with just Flask on its own and those e.g. requests, redis-py, psycopg2, pytz.