-
Notifications
You must be signed in to change notification settings - Fork 162
Doesn't work #1
Comments
It looks like you installed flask/werkzeug twice into that project, which in turn is causing import issues. For example, in my project, the server/lib/werkzeug directory does not contain a subdirectory called werkzeug. So you need to delete the duplicate directories, or perhaps just download the project again and this time don't run pip install, because when you download the project from developers.google.com/appengine, it already has the dependencies pre-installed. |
FYI, if you install with EDIT: After fiddling with various options, I decided to kill the directory where I was installing my deps (not using this skeleton but some other project), and after reinstalling the dependencies, it just worked... Weird. |
@foxbunny the instructions should states
|
Ok, so after having to deal with this issues many times over, here's my conclusion. The install will only succeed the first time (i.e., when target directory where you install deps is empty). If |
@foxbunny - Thanks! This post helped. The "pip install requirements.txt -t lib/" command is not idempotent in this context. Seems like a bug. Doing it exactly once does the trick. |
Solution:
|
I got the same problem when I installed Flask-KVSession because werkzeug is one of its dependencies. So, I used "--no-deps" option in pip. pip install --no-deps -t lib Flask-KVSession |
I got the same issue and it turned out to be resolved by flask versioning. For me, |
Log from GoogleAppEngineLauncher.app 1.8.9.1049
The text was updated successfully, but these errors were encountered: