Flask-Cache shows some import failure under dev_appserver that works without dev_appserver.
'Flask-Cache<0.8' in setup.py somehow works around it.
the full traceback
btw, this exception only happens when running the moin gae code under the GAE dev_appserver.
it does not happen when running code from default branch without GAE dev_appserver.
as our code is the same for both cases, i suspect that somehow the module import magic is misbehaving (see last line in the traceback, it tries to import jinja2 from the wrong namespace).
even if one avoids the jinja2 import using with_jinja2_ext=True, it'll just crash at another import due to same reason.
temporary workaround: http://hg.moinmo.in/moin/2.0/rev/9cc2a4e2f582
FYI - Flask-Cache version 10.1 changed imports from absolute to relative and now supports App Engine.
0.10.1 that is. thanks for notifying us here!
Can someone please test it (and whether flask-cache is the only such problem or other stuff still fails)?
hmm, looks like we have a quite similar issue for flask-themes running under the gae dev server. as flask-themes didn't change for long, what is causing this now?
Note: maybe the flask-themes issue is unrelated and was just a missing __init__.py in the flaskext package.
looks like it's fixed now (by new flask-cache and by the __init__.py fix). closing.
but: it seems like the change in flask-cache is only a workaround, so the fundamental issue in flask / appengine is still there.