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 requests can be changed to >=2.4.0,<=2.15.1.
The version constraint of dependency websocket-client can be changed to >=0.13.0,<=0.15.0.
The version constraint of dependency flask-admin can be changed to >=1.0.3,<=1.6.0.
The version constraint of dependency flask-wtf can be changed to >=0.9.0,<=0.15.1.
The version constraint of dependency flask-cors can be changed to >=1.7.0,<=3.0.10.
The version constraint of dependency tabulate can be changed to >=0.7.4,<=0.8.9.
The version constraint of dependency jsonschema can be changed to >=2.0.0,<=4.6.0.
The version constraint of dependency graphviz can be changed to >=0.3,<=0.20.
The version constraint of dependency ipaddress can be changed to >=1.0.3,<=1.0.23.
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 acitoolkit, 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 requests can be changed to >=2.4.0,<=2.15.1. The version constraint of dependency websocket-client can be changed to >=0.13.0,<=0.15.0. The version constraint of dependency flask-admin can be changed to >=1.0.3,<=1.6.0. The version constraint of dependency flask-wtf can be changed to >=0.9.0,<=0.15.1. The version constraint of dependency flask-cors can be changed to >=1.7.0,<=3.0.10. The version constraint of dependency tabulate can be changed to >=0.7.4,<=0.8.9. The version constraint of dependency jsonschema can be changed to >=2.0.0,<=4.6.0. The version constraint of dependency graphviz can be changed to >=0.3,<=0.20. The version constraint of dependency ipaddress can be changed to >=1.0.3,<=1.0.23.
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 requests
The calling methods from the websocket-client
The calling methods from the flask-admin
The calling methods from the flask-wtf
The calling methods from the flask-cors
The calling methods from the tabulate
The calling methods from the jsonschema
The calling methods from the graphviz
The calling methods from the ipaddress
@developer Could please help me check this issue? May I pull a request to fix it? Thank you very much.