Closed PyDeps closed 2 years ago
My apologies, but I am not interested in interacting with a bot.
Sorry to disturb you, but I am not a robot. I am doing a project to maintain the right versions of dependencies in python projects. If possible, I hope to submit a PR or communicate with you to help us better improve the detection accuracy. We can submit a PR or close this report.
Hi, In 3d-ken-burns, 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 gevent can be changed to >=0.10.0,<=21.12.0. The version constraint of dependency moviepy can be changed to >=0.2.1.7.15,<=2.0.0.dev2. The version constraint of dependency numpy can be changed to >=1.8.0,<=1.23.0rc3.
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 gevent
The calling methods from the moviepy
The calling methods from the numpy
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.