Hi, your project fast-marl requires "stable-baselines3==1.0" in its dependency. After analyzing the source code, we found that the following versions of stable-baselines3 can also be suitable without affecting your project, i.e., stable-baselines3 0.11.0, 0.11.1, 1.0rc2, 1.0rc1, 1.0rc0, 1.1.0a3. Therefore, we suggest to loosen the dependency on stable-baselines3 from "stable-baselines3==1.0" to "stable-baselines3>=0.11.0,<=1.1.0a3" to avoid any possible conflict for importing more packages or for downstream projects that may use fast-marl.
May I pull a request to further loosen the dependency on stable-baselines3?
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 fast-marl directly uses 4 APIs from package stable-baselines3.
Beginning from the 4 APIs above, 11 functions are then indirectly called, including -4 stable-baselines3's internal APIs and 15 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan stable-baselines3's versions and observe that during its evolution between any version from [0.11.0, 0.11.1, 1.0rc2, 1.0rc1, 1.0rc0, 1.1.0a3] and 1.0, 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 collections, numpy and multiprocessing are called by stable-baselines3 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 stable-baselines3 from "stable-baselines3==1.0" to "stable-baselines3>=0.11.0,<=1.1.0a3". This will improve the applicability of fast-marl and reduce the possibility of any further dependency conflict with other projects.
semitable
commented
2 years ago 
Agnes-U
Hi, your project fast-marl requires "stable-baselines3==1.0" in its dependency. After analyzing the source code, we found that the following versions of stable-baselines3 can also be suitable without affecting your project, i.e., stable-baselines3 0.11.0, 0.11.1, 1.0rc2, 1.0rc1, 1.0rc0, 1.1.0a3. Therefore, we suggest to loosen the dependency on stable-baselines3 from "stable-baselines3==1.0" to "stable-baselines3>=0.11.0,<=1.1.0a3" to avoid any possible conflict for importing more packages or for downstream projects that may use fast-marl.
May I pull a request to further loosen the dependency on stable-baselines3?
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 fast-marl directly uses 4 APIs from package stable-baselines3.
Beginning from the 4 APIs above, 11 functions are then indirectly called, including -4 stable-baselines3's internal APIs and 15 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan stable-baselines3's versions and observe that during its evolution between any version from [0.11.0, 0.11.1, 1.0rc2, 1.0rc1, 1.0rc0, 1.1.0a3] and 1.0, 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 collections, numpy and multiprocessing are called by stable-baselines3 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 stable-baselines3 from "stable-baselines3==1.0" to "stable-baselines3>=0.11.0,<=1.1.0a3". This will improve the applicability of fast-marl and reduce the possibility of any further dependency conflict with other projects.