Adding six==1.9.0 resolves the issue. The content of the modified requirements.txt: Flask==1.0.2 six==1.9.0 flask-talisman==0.7.0
Maybe my post will help someone else stumbling over the same issue. Curious, why this can happen while using the same versions of the different modules. Some modules have changed and which loaded which I don't explicitly mention in requirements.txt On Friday, August 14, 2020 at 12:16:18 PM UTC-4 Karl-Heinz Müller wrote: > Hi, while updating the application today, I noticed that flask-talisman > throws an error. > > File "/env/lib/python3.7/site-packages/flask_talisman/talisman.py", line > 17, in <module> from six import iteritems, string_types > ModuleNotFoundError: No module named 'six' > > I use the same versions for flask and flask_talisman version as before and > set in requirements.txt > > Flask==1.0.2 > flask-talisman==0.7.0 > > I tried to fix the error by adding six to the requirements. This didn't > resolve the issue. Wondering why continue using the same modules, this > error suddenly appears and which combinations of modules allow me to > continue using flask-talisman. > > For now I temporarily commented out the talisman. > > Is it a temporal glitch/bug? What can I do to run flask-talisman on > GAE/Python3.7? > Please let me know what additional information you need to know. > > Thanks > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/b10bd4c1-a8fb-404f-9104-2e313b09d3c8n%40googlegroups.com.
