remcoboerma / breaking_nameko Goto Github PK

Dear developers,

Your project breaking_nameko requires "nameko==2.13.0" in its dependency. After analyzing the source code, we found that the following versions of nameko can also be suitable without affecting your project, i.e., nameko 2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.8.5, 2.9.0rc0, 2.9.0, 2.9.0-rc0, 2.9.1rc0, 2.9.1, 2.9.1-rc0, 2.10.0, 2.11.0, 2.12.0, 2.14.0, 2.14.1, 3.0.0rc11, 3.0.0rc10, 3.0.0rc9, 3.0.0rc8, 3.0.0rc7, 3.0.0rc6, 3.0.0rc5, 3.0.0rc4, 3.0.0rc3, 3.0.0rc2, 3.0.0rc1, 3.0.0rc0, 3.0.0-rc11, 3.0.0-rc10, 3.0.0-rc9, 3.0.0-rc8, 3.0.0-rc7, 3.0.0-rc6, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-rc0. Therefore, we suggest to loosen the dependency on nameko from "nameko==2.13.0" to "nameko>=2.6.0,<=3.0.0-rc11" to avoid any possible conflict for importing more packages or for downstream projects that may use ddos_script.

May I pull a request to further loosen the dependency on nameko?

By the way, could you please tell us whether such dependency analysis may be potentially helpful for maintaining dependencies easier during your development?

Details:

Your project (commit id: 4039359) directly uses 1 APIs from package nameko.

nameko.extensions.Entrypoint.decorator

Beginning fromwhich, 2 functions are then indirectly called, including 1 nameko's internal APIs and 1 outsider APIs as follows:

[/remcoboerma/breaking_nameko]
+--nameko.extensions.Entrypoint.decorator
|      +--nameko.extensions.register_entrypoint
|      +--functools.partial

Since all these functions have not been changed between any version for package "nameko" from [2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.8.5, 2.9.0rc0, 2.9.0, 2.9.0-rc0, 2.9.1rc0, 2.9.1, 2.9.1-rc0, 2.10.0, 2.11.0, 2.12.0, 2.14.0, 2.14.1, 3.0.0rc11, 3.0.0rc10, 3.0.0rc9, 3.0.0rc8, 3.0.0rc7, 3.0.0rc6, 3.0.0rc5, 3.0.0rc4, 3.0.0rc3, 3.0.0rc2, 3.0.0rc1, 3.0.0rc0, 3.0.0-rc11, 3.0.0-rc10, 3.0.0-rc9, 3.0.0-rc8, 3.0.0-rc7, 3.0.0-rc6, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-rc0] and 2.13.0. Therefore, we believe it is safe to loosen the corresponding dependency.