The other main difference is Django is developed as part of a large organization, Flask is not. Get the right people together and that could be fixed easily...
I use Werkzeug directly rather than Flask, so I can't speak to whether Flask is abandonware or not, but I'm very happy with Werkzeug. With very little effort, I get to build just enough framework for my application, without having to be shoehorned into someone else's tradeoffs.
Have you tried out Falcon, btw? If so, how does it compare to Werkzeug?
They add tons. There are many commits, bug fixes, etc. It's just that there A) hasn't been a release to PyPi, B) is an inordinate quantity of unmerged pull requests, C) are many undocumented changes, and D) issues like https://github.com/mitsuhiko/flask/issues/1272 that are over a year old (I left a comment https://github.com/mitsuhiko/flask/issues/1575#issuecomment-... explaining the vicious circle that I believe is created by not releasing to PyPi). I commit to Django (and donate), but I would never commit to Flask when it makes no attempt at Industry Standards™ like PyPi releases.
I shouldn't have said it's "abandoned", because that's an insult to the parts of the community that are very active.
Im wondering what's a suitable alternative.... with SQLAlchemy and Celery/RQ integration?
Flask is basically abandoned, despite continually receiving undocumented commits.
Flask hasn't even had a PyPi release, or even a Git tag for that matter, since June, 2013. The documentation is also far behind.