The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict.
The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.
After further analysis, in this project,
The version constraint of dependency alembic can be changed to >=0.1.0,<=0.1.1.
The version constraint of dependency Flask-Babel can be changed to >=0.9,<=2.0.0.
The version constraint of dependency Flask-HTTPAuth can be changed to >=3.0.0,<=4.7.0.
The version constraint of dependency Flask-Login can be changed to >=0.1.3,<=0.6.2.
The version constraint of dependency Flask-Mail can be changed to >=0.7.0,<=0.7.6.
The version constraint of dependency Flask-Mail can be changed to >=0.9.0,<=0.9.1.
The version constraint of dependency Flask-Moment can be changed to >=0.1.0,<=0.11.0.
The version constraint of dependency Flask-Moment can be changed to >=1.0.1,<=1.0.2.
The version constraint of dependency Flask-SQLAlchemy can be changed to >=0.16,<=3.0.0a1.
The version constraint of dependency PyJWT can be changed to >=0.1.1,<=1.1.0.
The version constraint of dependency redis can be changed to >=3.0.0,<=4.3.3.
The version constraint of dependency requests can be changed to >=0.2.1,<=0.2.3.
The version constraint of dependency requests can be changed to >=0.7.0,<=2.24.0.
The version constraint of dependency requests can be changed to ==2.26.0.
The version constraint of dependency rq can be changed to >=0.3.3,<=1.10.1.
The version constraint of dependency SQLAlchemy can be changed to >=0.5.0beta3,<=1.4.41.
The version constraint of dependency Werkzeug can be changed to >=0.9,<=2.1.2.
The version constraint of dependency WTForms can be changed to >=1.0.2,<=3.0.1.
The above modification suggestions can reduce the dependency conflicts as much as possible,
and introduce the latest version as much as possible without calling Error in the projects.
The invocation of the current project includes all the following methods.
Hi, In microblog, inappropriate dependency versioning constraints can cause risks.
Below are the dependencies and version constraints that the project is using
The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict. The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.
After further analysis, in this project, The version constraint of dependency alembic can be changed to >=0.1.0,<=0.1.1. The version constraint of dependency Flask-Babel can be changed to >=0.9,<=2.0.0. The version constraint of dependency Flask-HTTPAuth can be changed to >=3.0.0,<=4.7.0. The version constraint of dependency Flask-Login can be changed to >=0.1.3,<=0.6.2. The version constraint of dependency Flask-Mail can be changed to >=0.7.0,<=0.7.6. The version constraint of dependency Flask-Mail can be changed to >=0.9.0,<=0.9.1. The version constraint of dependency Flask-Moment can be changed to >=0.1.0,<=0.11.0. The version constraint of dependency Flask-Moment can be changed to >=1.0.1,<=1.0.2. The version constraint of dependency Flask-SQLAlchemy can be changed to >=0.16,<=3.0.0a1. The version constraint of dependency PyJWT can be changed to >=0.1.1,<=1.1.0. The version constraint of dependency redis can be changed to >=3.0.0,<=4.3.3. The version constraint of dependency requests can be changed to >=0.2.1,<=0.2.3. The version constraint of dependency requests can be changed to >=0.7.0,<=2.24.0. The version constraint of dependency requests can be changed to ==2.26.0. The version constraint of dependency rq can be changed to >=0.3.3,<=1.10.1. The version constraint of dependency SQLAlchemy can be changed to >=0.5.0beta3,<=1.4.41. The version constraint of dependency Werkzeug can be changed to >=0.9,<=2.1.2. The version constraint of dependency WTForms can be changed to >=1.0.2,<=3.0.1.
The above modification suggestions can reduce the dependency conflicts as much as possible, and introduce the latest version as much as possible without calling Error in the projects.
The invocation of the current project includes all the following methods.
The calling methods from the alembic
The calling methods from the Flask-Babel
The calling methods from the Flask-HTTPAuth
The calling methods from the Flask-Login
The calling methods from the Flask-Mail
The calling methods from the Flask-Moment
The calling methods from the Flask-SQLAlchemy
The calling methods from the PyJWT
The calling methods from the redis
The calling methods from the requests
The calling methods from the rq
The calling methods from the SQLAlchemy
The calling methods from the Werkzeug
The calling methods from the WTForms
The calling methods from the all methods
@developer Could please help me check this issue? May I pull a request to fix it? Thank you very much.