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 aria2p can be changed to >=0.2.0,<=0.9.1.
The version constraint of dependency beautifulsoup4 can be changed to >=4.10.0,<=4.11.1.
The version constraint of dependency google-api-python-client can be changed to >=1.4.0,<=2.51.0.
The version constraint of dependency lk21 can be changed to ==1.6.0.
The version constraint of dependency psutil can be changed to >=1.0.0,<=5.9.1.
The version constraint of dependency pillow can be changed to ==9.2.0.
The version constraint of dependency pillow can be changed to >=2.0.0,<=9.1.1.
The version constraint of dependency cfscrape can be changed to >=1.3,<=1.4.1.
The version constraint of dependency cfscrape can be changed to >=1.4.3,<=1.6.1.
The version constraint of dependency Pyrogram can be changed to >=1.0.0,<=2.0.57.
The version constraint of dependency python-magic can be changed to >=0.4.0,<=0.4.18.
The version constraint of dependency python-magic can be changed to >=0.4.20,<=0.4.27.
The version constraint of dependency python-telegram-bot can be changed to >=4.0rc1,<=13.12.
The version constraint of dependency requests can be changed to >=0.10.1,<=2.24.0.
The version constraint of dependency requests can be changed to ==2.26.0.
The version constraint of dependency yt-dlp can be changed to >=2021.2.24,<=2022.9.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 mirrorbot137, 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 aria2p can be changed to >=0.2.0,<=0.9.1. The version constraint of dependency beautifulsoup4 can be changed to >=4.10.0,<=4.11.1. The version constraint of dependency google-api-python-client can be changed to >=1.4.0,<=2.51.0. The version constraint of dependency lk21 can be changed to ==1.6.0. The version constraint of dependency psutil can be changed to >=1.0.0,<=5.9.1. The version constraint of dependency pillow can be changed to ==9.2.0. The version constraint of dependency pillow can be changed to >=2.0.0,<=9.1.1. The version constraint of dependency cfscrape can be changed to >=1.3,<=1.4.1. The version constraint of dependency cfscrape can be changed to >=1.4.3,<=1.6.1. The version constraint of dependency Pyrogram can be changed to >=1.0.0,<=2.0.57. The version constraint of dependency python-magic can be changed to >=0.4.0,<=0.4.18. The version constraint of dependency python-magic can be changed to >=0.4.20,<=0.4.27. The version constraint of dependency python-telegram-bot can be changed to >=4.0rc1,<=13.12. The version constraint of dependency requests can be changed to >=0.10.1,<=2.24.0. The version constraint of dependency requests can be changed to ==2.26.0. The version constraint of dependency yt-dlp can be changed to >=2021.2.24,<=2022.9.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 aria2p
The calling methods from the beautifulsoup4
The calling methods from the google-api-python-client
The calling methods from the lk21
The calling methods from the psutil
The calling methods from the pillow
The calling methods from the cfscrape
The calling methods from the Pyrogram
The calling methods from the python-magic
The calling methods from the python-telegram-bot
The calling methods from the requests
The calling methods from the yt-dlp
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.