You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, your project rqalpha-mod-sentry(commit id: d36167a) requires "rqalpha==2.1.1" in its dependency. After analyzing the source code, we found that the following versions of rqalpha can also be suitable, i.e., rqalpha 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17, 0.0.18, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.0.24, 0.0.26, 0.0.50, 0.0.51, 0.0.52, 0.0.53, 0.0.54, 0.0.55, 0.0.56, 0.0.57, 0.0.58, 0.0.59, 0.0.60, 0.0.61, 0.0.62, 0.0.63, 0.0.64, 0.0.65, 0.0.66, 0.0.67, 0.0.68, 0.0.69, 0.0.70, 0.0.71, 0.0.72, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.3.7, 0.3.8, 0.3.9, 0.3.10, 0.3.11, 0.3.12, 0.3.13, 0.3.14, 0.3.15, 0.3.16, 2.0.0b0, 2.0.0, 2.0.0-beta, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.1.0, since all functions that you directly (2 APIs: rqalpha.interface.AbstractMod.init, rqalpha.main.cli) or indirectly (propagate to -2 rqalpha's internal APIs and 0 outsider APIs) used from the package have not been changed in these versions, thus not affecting your usage.
Therefore, we believe that it is quite safe to loose your dependency on rqalpha from "rqalpha==2.1.1" to "rqalpha>=0.0.9,<=2.1.1". This will improve the applicability of rqalpha-mod-sentry and reduce the possibility of any further dependency conflict with other projects.
May I pull a request to further loosen the dependency on rqalpha?
By the way, could you please tell us whether such an automatic tool for dependency analysis may be potentially helpful for maintaining dependencies easier during your development?
The text was updated successfully, but these errors were encountered:
Hi, your project rqalpha-mod-sentry(commit id: d36167a) requires "rqalpha==2.1.1" in its dependency. After analyzing the source code, we found that the following versions of rqalpha can also be suitable, i.e., rqalpha 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17, 0.0.18, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.0.24, 0.0.26, 0.0.50, 0.0.51, 0.0.52, 0.0.53, 0.0.54, 0.0.55, 0.0.56, 0.0.57, 0.0.58, 0.0.59, 0.0.60, 0.0.61, 0.0.62, 0.0.63, 0.0.64, 0.0.65, 0.0.66, 0.0.67, 0.0.68, 0.0.69, 0.0.70, 0.0.71, 0.0.72, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.3.7, 0.3.8, 0.3.9, 0.3.10, 0.3.11, 0.3.12, 0.3.13, 0.3.14, 0.3.15, 0.3.16, 2.0.0b0, 2.0.0, 2.0.0-beta, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.1.0, since all functions that you directly (2 APIs: rqalpha.interface.AbstractMod.init, rqalpha.main.cli) or indirectly (propagate to -2 rqalpha's internal APIs and 0 outsider APIs) used from the package have not been changed in these versions, thus not affecting your usage.
Therefore, we believe that it is quite safe to loose your dependency on rqalpha from "rqalpha==2.1.1" to "rqalpha>=0.0.9,<=2.1.1". This will improve the applicability of rqalpha-mod-sentry and reduce the possibility of any further dependency conflict with other projects.
May I pull a request to further loosen the dependency on rqalpha?
By the way, could you please tell us whether such an automatic tool for dependency analysis may be potentially helpful for maintaining dependencies easier during your development?
The text was updated successfully, but these errors were encountered: