Hi, your project Youtube-Downloader-by-PyTube requires "pytube==11.0.1" in its dependency. After analyzing the source code, we found that the following versions of pytube can also be suitable without affecting your project, i.e., pytube 11.0.0, 11.0.2, 12.0.0. Therefore, we suggest to loosen the dependency on pytube from "pytube==11.0.1" to "pytube>=11.0.0,<=12.0.0" to avoid any possible conflict for importing more packages or for downstream projects that may use Youtube-Downloader-by-PyTube.
May I pull a request to further loosen the dependency on pytube?
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 Youtube-Downloader-by-PyTube directly uses 1 APIs from package pytube.
pytube.__main__.YouTube.__init__
Beginning from the 1 APIs above, 9 functions are then indirectly called, including 5 pytube's internal APIs and 4 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan pytube's versions and observe that during its evolution between any version from [11.0.0, 11.0.2, 12.0.0] and 11.0.1, 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).
As for other packages, the APIs of urllib and re are called by pytube in the call graph and the dependencies on these packages also stay the same in our suggested versions, thus avoiding any outside conflict.
Therefore, we believe that it is quite safe to loose your dependency on pytube from "pytube==11.0.1" to "pytube>=11.0.0,<=12.0.0". This will improve the applicability of Youtube-Downloader-by-PyTube and reduce the possibility of any further dependency conflict with other projects.
Hi, your project Youtube-Downloader-by-PyTube requires "pytube==11.0.1" in its dependency. After analyzing the source code, we found that the following versions of pytube can also be suitable without affecting your project, i.e., pytube 11.0.0, 11.0.2, 12.0.0. Therefore, we suggest to loosen the dependency on pytube from "pytube==11.0.1" to "pytube>=11.0.0,<=12.0.0" to avoid any possible conflict for importing more packages or for downstream projects that may use Youtube-Downloader-by-PyTube.
May I pull a request to further loosen the dependency on pytube?
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 Youtube-Downloader-by-PyTube directly uses 1 APIs from package pytube.
Beginning from the 1 APIs above, 9 functions are then indirectly called, including 5 pytube's internal APIs and 4 outsider APIs. The specific call graph is listed as follows (neglecting some repeated function occurrences).
We scan pytube's versions and observe that during its evolution between any version from [11.0.0, 11.0.2, 12.0.0] and 11.0.1, 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).
As for other packages, the APIs of urllib and re are called by pytube in the call graph and the dependencies on these packages also stay the same in our suggested versions, thus avoiding any outside conflict.
Therefore, we believe that it is quite safe to loose your dependency on pytube from "pytube==11.0.1" to "pytube>=11.0.0,<=12.0.0". This will improve the applicability of Youtube-Downloader-by-PyTube and reduce the possibility of any further dependency conflict with other projects.