Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggest to loosen the dependency on nameko #2

Open
Agnes-U opened this issue Nov 9, 2022 · 0 comments
Open

Suggest to loosen the dependency on nameko #2

Agnes-U opened this issue Nov 9, 2022 · 0 comments

Comments

@Agnes-U
Copy link

Agnes-U commented Nov 9, 2022

Hi, your project py-weather-micro-service(commit id: 425ced5) requires "nameko==2.11.0" in its dependency. After analyzing the source code, we found that the following versions of nameko can also be suitable, i.e., nameko 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, since all functions that you directly (3 APIs: nameko.extensions.Entrypoint.decorator, nameko.standalone.rpc.ClusterRpcProxy.init, nameko.rpc.RpcProxy.init) or indirectly (propagate to 4 nameko's internal APIs and 1 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 nameko from "nameko==2.11.0" to "nameko>=2.7.0,<=2.11.0". This will improve the applicability of py-weather-micro-service and reduce the possibility of any further dependency conflict with other projects.

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

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant