Updated to Flask-WTF 0.9.3

[mdxs]

Updated to Flask-WTF 0.9.3; note that this requires us to import wtforms and wtforms.validators ourselves: see https://flask-wtf.readthedocs.org/en/latest/upgrade.html#version-0-9-0 reading: "Dropping the imports of wtforms is a big change, it may be lots of pain for you, but the imports are hard to maintain. Instead of importing Fields from Flask-WTF, you need to import them from the original wtforms" (and this applies to the validators as well).

[lipis]

I also wanted to do some upgrades here but I'm basically waiting for the WTForms to release the final version 2.0 in order to touch Flask-WTF, because I don't want to break backwards compatibilities too often.. Thanks but I think, this one will be revised when it's time.. for now it works nicely :)

[lipis]

Forgot the link that I wanted to post: http://wtforms.readthedocs.org/en/latest/whats_new.html

[topless]

Great eye .. we missed couple of updates. Irrelevant but maybe we should put down all the backwards incompatible changes for version 2.

1. modelq, dedicated model methods for the queries. It will clean up a lot the handlers and will improve modularity.
2. Lazy loading. I think this one is a must. It will boost performance of the application, especially while it grows.
   http://flask.pocoo.org/docs/patterns/lazyloading/

[mdxs]

The last commit is based on http://flask.pocoo.org/docs/extensiondev/#anatomy-of-an-extension showing that the flask.ext. notation can be followed to find the extensions (which in recent incarnations of Flask are all moving towards a more maintainable structure).

[mdxs]

The same article referred to above shows that flask_wtf (as it is also named in the original source: https://github.com/lepture/flask-wtf/tree/master/flask_wtf) can sit in our main/lib/ while the flask.ext does it's magic to resolve imports from flask.ext.wtf (this seems to be a common pattern for Flask extensions).

[mdxs]

After moving relevant changes and background information here, the gae-init-babel specific PR was closed in favour of this PR in the gae-init parent project. Though acceptance is likely to be postponed, I hope this PR helps document the steps taken and the rationale behind them. This PR may become obsolete if WTForms 2.0 releases... though I wonder whether that would make Flask-WTF itself obsolete.

[mdxs]

The Flask-WTF project is tracking WTForms 2.0 also, see wtforms/flask-wtf#94

[lipis]

Now we just have to see who is going to deliver first... and if we could drop one of them would be also cool to have less dependencies.. Much appreciated the research that you're making... I'll buy you a beer when we'll be in the same city at one point :D

[mdxs]

Thanks. I will probable need to read up on WTForms, but I thought Flask-WTF glued WTForms to Flask; and thus we would continue to use it (unless it would become obsolete/pointless when all features are in WTForms 2.0...)

[mdxs]

Superseded by #59 "Update Flask-WTF to 0.9.4" which is a much cleaner PR because of steps already taken in gae-init recently.