Skip to content

Suggest to loosen the dependency on tweepy #8

@Agnes-U

Description

@Agnes-U

Dear developers,

Your project TgTwitterBot requires "tweepy==4.3.0" in its dependency. After analyzing the source code, we found that the following versions of tweepy can also be suitable without affecting your project, i.e., tweepy 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.4.0. Therefore, we suggest to loosen the dependency on tweepy from "tweepy==4.3.0" to "tweepy>=4.0.0,<=4.4.0" 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 tweepy?

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: 2462c65) directly uses 3 APIs from package tweepy.

tweepy.api.API.__init__, tweepy.auth.OAuthHandler.__init__, tweepy.auth.OAuthHandler.set_access_token

Beginning fromwhich, 3 functions are then indirectly called, including 0 tweepy's internal APIs and 3 outsider APIs as follows:

[/New-dev0/TgTwitterBot]
+--tweepy.api.API.__init__
|      +--tweepy.parsers.ModelParser.__init__
|      +--platform.python_version
|      +--requests.Session
+--tweepy.auth.OAuthHandler.__init__
|      +--requests_oauthlib.OAuth1Session
+--tweepy.auth.OAuthHandler.set_access_token

Since all these functions have not been changed between any version for package "tweepy" from [4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.4.0] and 4.3.0. Therefore, we believe it is safe to loosen the corresponding dependency.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions