Closed zacqed closed 2 years ago
I ran into this same problem. I was able to work around it by reverting to Flask-User==0.6. (Note that this will require changes to your code.)
I'm not 100% sure, but the root cause might be related to these issues within setuptools:
If that is the root cause, then it might help to move Flask
to the end of install_requires
in setup.py.
Not OP but I tried moving Flask to the end of install_requires on a custom package... didn't work :( Thanks for the suggestion though
Yeah this issue is blocking me too.
Update: I forked to here: https://github.com/wayne-li2/Flask-User And uploaded to PyPi under 'Flask-User-AWS==1.0.1.7' (pip install Flask-User-AWS) And the Elastic Beanstalk build passed. I tried moving Flask to the bottom of 'install_requires' but that didn't work. Then I tried that + remove 'Flask-Login' from setup_requires, and that seemed to work. However, I have no idea how breaking this will be for Flask-User itself. So use with caution.
I have just deployed @wayne-li2 release on Heroku successfully.
I had a similar issue with pip installation on CircleCI. I made the "remove 'Flask-Login' from setup_requires" change to @wayne-li2 in own fork here and the installation proceeded without an error.
See my fork here: https://github.com/sdpetrides/Flask-User/tree/circleci-pip-install
@wayne-li2 's release works on CircleCI as well.
I was able to work around it by reverting to Flask-User==0.6.
A bit late, so merely for future readers: it seems that specifying any version may solve this, so: specifying the current version may be doing the trick as well.
Flask_User is breaking the installation on AWS using ElasticBeanStalk. The specific portion of the error log is as follows:
Any help on the issue would be appreciated. It seems flask_user is unable to identify the existing installation of Flask library.