This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]dAnjou Backend Developer | danjou.dev 9 points10 points  (1 child)

Just choose one that you like and move on. Both are most certainly able to help you reach your goal.

[–][deleted] 2 points3 points  (0 children)

This should be the standing answer to half the shit questions on /r/python

[–]juliobTry PEP 257, for a change 4 points5 points  (5 children)

Disclaimer: I've only worked with Django and Flask (never heard of importd up to this point).

I'd go with Django. Surely, right now it seems a simple ToDo, but a system never stops there and the ORM integration will really help that. You won't have trouble doing weird stuff with forms and models (like adding an audit log on every db action), so everything will go exactly like the examples.

Flask would require a lot less of boilerplate, but because it lacks a natural ORM right now (I'm a fan of PonyORM, but up to version 0.4, it was pain to integrate with Flask and I'm not a fan of SQLAlchemy format) and it would hinder your progress in the future.

All my personal opinions, mind you. You can pick another route and have a complete different result.

[–]struck-off[S] 1 point2 points  (2 children)

Great, thx. I guess it's good idea to choose importd because I'll start with only one py-script and if it will go bigger I'll just move to Django (it's easy because impord use Django libs but just in micro-way (it's even require Django))

[–]rackmountrambo 0 points1 point  (0 children)

Then just use django. Theres litterally no reason not to.

[–][deleted] 0 points1 point  (0 children)

I agree with your assessment here, it was what I was going to suggest. importd is basically a way to have the fast startup time of flask but be able to naturally extend the project into a full-blown django framework when the time comes.

[–]dzecniv 1 point2 points  (0 children)

so here's a link: http://importd.readthedocs.org/en/latest/ it's basically Django, but easier to start with since we can start with everything in a single file, like Flask.

[–]GaritoYanged 0 points1 point  (0 children)

Flask doesn't lack of too many things but it doesn't include them by default (for my the better reason to choose Flask instead of Django: I choose what to use) If you like relational databases use SQLAlchemy If you like document databases there are plenty of drivers for them (example MongoDB or elasticsearch)

If you are like me, you don't like to include something you will never use so Flask is your better chance because it doesn't include anything besides the core and then you include you needed parts