3 ms·
Flask has a much larger pool of community extensions, and in general has more community support and more "batteries included" than Bottle. In my opinion, there
by RussianCow 12y ago
Flask has a much larger pool of community extensions, and in general has more community support and more "batteries included" than Bottle. In my opinion, there is no real reason to use Bottle anymore.
- bpicolo 12y agoCommunity extensions are exactly what I dislike about Flask. I want extensibility without custom extensions. I want the framework to be out of the way entirely when I choose additional packages to work with.
- detaro 12y agothen don't use the extensions? Not trying to be snarky, I might be missing something, but does Flask actually make it harder to use additional packages?
- corford 12y agoNope. You can use whatever packages you like. Those you've rolled yourself, standard python packages like psycopg2, redis-py etc., Flask community provided packages and anything in between. I'm building a fairly large webapp in Flask and rarely, if at all, use any Flask packages other than the core itself.
- rcarmo 12y agoHmmm. I get nice templating and very straightforward routing with Bottle. Why shouldn't I use that, especially since I can review the whole codebase in half an hour?
- RussianCow 12y agoDo you not get that with Flask?
- rcarmo 12y agoFlask has always struck me as requiring too many plugins. With bottle, I just drop one file into my work dir and I'm off. Toss in Peewee as well (another single file) and I get a decent ORM. That combination is more flexible and productive for me than Flask. (also, I already have a nice template for bigger projects: https://github.com/rcarmo/ink-bottle https://github.com/rcarmo/ink-bottle)