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 pkuseg #8

Open
Agnes-U opened this issue Dec 12, 2022 · 0 comments
Open

Suggest to loosen the dependency on pkuseg #8

Agnes-U opened this issue Dec 12, 2022 · 0 comments

Comments

@Agnes-U
Copy link

Agnes-U commented Dec 12, 2022

Dear developers,

Your project g2pC requires "pkuseg==0.0.22" in its dependency. After analyzing the source code, we found that the following versions of pkuseg can also be suitable without affecting your project, i.e., pkuseg 0.0.21. Therefore, we suggest to loosen the dependency on pkuseg from "pkuseg==0.0.22" to "pkuseg>=0.0.21,<=0.0.22" 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 pkuseg?

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: 869f36f) directly uses 1 APIs from package pkuseg.

pkuseg.__init__.pkuseg.__init__

Beginning fromwhich, 35 functions are then indirectly called, including 12 pkuseg's internal APIs and 23 outsider APIs as follows:

[/Kyubyong/g2pC]
+--pkuseg.__init__.pkuseg.__init__

Since all these functions have not been changed between any version for package "pkuseg" from [0.0.21] and 0.0.22. Therefore, we believe it is safe to loosen the corresponding dependency.

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