Hi, your project TGBot requires "aiogram==2.19" in its dependency. After analyzing the source code, we found that the following versions of aiogram can also be suitable without affecting your project, i.e., aiogram 2.18, 2.20. Therefore, we suggest to loosen the dependency on aiogram from "aiogram==2.19" to "aiogram>=2.18,<=2.20" to avoid any possible conflict for importing more packages or for downstream projects that may use TGBot.
May I pull a request to further loosen the dependency on aiogram?
By the way, could you please tell us whether such dependency analysis may be potentially helpful for maintaining dependencies easier during your development?
We also give our detailed analysis as follows for your reference:
Your project TGBot directly uses 7 APIs from package aiogram.
Beginning from the 7 APIs above, 36 functions are then indirectly called, including 27 aiogram's internal APIs and 9 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan aiogram's versions and observe that during its evolution between any version from [2.18, 2.20] and 2.19, the changing functions (diffs being listed below) have none intersection with any function or API we mentioned above (either directly or indirectly called by this project).
As for other packages, the APIs of secrets, ssl, certifi, aiohttp_socks, inspect, functools and asyncio are called by aiogram in the call graph and the dependencies on these packages also stay the same in our suggested versions, thus avoiding any outside conflict.
Therefore, we believe that it is quite safe to loose your dependency on aiogram from "aiogram==2.19" to "aiogram>=2.18,<=2.20". This will improve the applicability of TGBot and reduce the possibility of any further dependency conflict with other projects.
SaryalVasilyev
commented
1 year ago
Hi, your project TGBot requires "aiogram==2.19" in its dependency. After analyzing the source code, we found that the following versions of aiogram can also be suitable without affecting your project, i.e., aiogram 2.18, 2.20. Therefore, we suggest to loosen the dependency on aiogram from "aiogram==2.19" to "aiogram>=2.18,<=2.20" to avoid any possible conflict for importing more packages or for downstream projects that may use TGBot.
May I pull a request to further loosen the dependency on aiogram?
By the way, could you please tell us whether such dependency analysis may be potentially helpful for maintaining dependencies easier during your development?
We also give our detailed analysis as follows for your reference:
Your project TGBot directly uses 7 APIs from package aiogram.
Beginning from the 7 APIs above, 36 functions are then indirectly called, including 27 aiogram's internal APIs and 9 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan aiogram's versions and observe that during its evolution between any version from [2.18, 2.20] and 2.19, the changing functions (diffs being listed below) have none intersection with any function or API we mentioned above (either directly or indirectly called by this project).
As for other packages, the APIs of secrets, ssl, certifi, aiohttp_socks, inspect, functools and asyncio are called by aiogram in the call graph and the dependencies on these packages also stay the same in our suggested versions, thus avoiding any outside conflict.
Therefore, we believe that it is quite safe to loose your dependency on aiogram from "aiogram==2.19" to "aiogram>=2.18,<=2.20". This will improve the applicability of TGBot and reduce the possibility of any further dependency conflict with other projects.