Hi, your project EXTRACTOR requires "textblob==0.15.3" in its dependency. After analyzing the source code, we found that the following versions of textblob can also be suitable without affecting your project, i.e., textblob 0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.11.1, 0.12.0, 0.13.0, 0.13.1, 0.14.0, 0.15.0, 0.15.1, 0.15.2, 0.16.0, 0.17.0, 0.17.1. Therefore, we suggest to loosen the dependency on textblob from "textblob==0.15.3" to "textblob>=0.9.0,<=0.17.1" to avoid any possible conflict for importing more packages or for downstream projects that may use EXTRACTOR.
May I pull a request to further loosen the dependency on textblob?
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 EXTRACTOR directly uses 1 APIs from package textblob.
textblob.blob.TextBlob.__init__
Beginning from the 1 APIs above, 5 functions are then indirectly called, including 5 textblob's internal APIs and 0 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan textblob's versions and observe that during its evolution between any version from [0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.11.1, 0.12.0, 0.13.0, 0.13.1, 0.14.0, 0.15.0, 0.15.1, 0.15.2, 0.16.0, 0.17.0, 0.17.1] and 0.15.3, 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).
Therefore, we believe that it is quite safe to loose your dependency on textblob from "textblob==0.15.3" to "textblob>=0.9.0,<=0.17.1". This will improve the applicability of EXTRACTOR and reduce the possibility of any further dependency conflict with other projects.
Hi, your project EXTRACTOR requires "textblob==0.15.3" in its dependency. After analyzing the source code, we found that the following versions of textblob can also be suitable without affecting your project, i.e., textblob 0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.11.1, 0.12.0, 0.13.0, 0.13.1, 0.14.0, 0.15.0, 0.15.1, 0.15.2, 0.16.0, 0.17.0, 0.17.1. Therefore, we suggest to loosen the dependency on textblob from "textblob==0.15.3" to "textblob>=0.9.0,<=0.17.1" to avoid any possible conflict for importing more packages or for downstream projects that may use EXTRACTOR.
May I pull a request to further loosen the dependency on textblob?
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 EXTRACTOR directly uses 1 APIs from package textblob.
Beginning from the 1 APIs above, 5 functions are then indirectly called, including 5 textblob's internal APIs and 0 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan textblob's versions and observe that during its evolution between any version from [0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.11.1, 0.12.0, 0.13.0, 0.13.1, 0.14.0, 0.15.0, 0.15.1, 0.15.2, 0.16.0, 0.17.0, 0.17.1] and 0.15.3, 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).
Therefore, we believe that it is quite safe to loose your dependency on textblob from "textblob==0.15.3" to "textblob>=0.9.0,<=0.17.1". This will improve the applicability of EXTRACTOR and reduce the possibility of any further dependency conflict with other projects.