Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove gevent monkeypatching. #287
Open
Conversation
For somebody using this package as a library, it would be preferable to leave whether to monkeypatch gevent into the standard library up to the user, rather than forcing it on every consumer. As far as I can tell, the only place that monkeypatching is used, is for interacting with requests. The only place this is *directly* used by the client is in `steam.core.CMClient.boostrap_from_webapi`, which is only called on the initial connection. Letting that call be synchronous, if the user doesn't want to use gevent directly seems reasonable.
|
Kudos, SonarCloud Quality Gate passed!
|
|
You are correct. I've been intending to remove monkey patch to make the code easier to use in conjunction with other libraries and features of python. That webapi call, and another webapi method, are the only places where library might needed. Of course the user could be using |
|
This will also affect |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
For somebody using this package as a library, it would be preferable to leave
whether to monkeypatch gevent into the standard library up to the user, rather
than forcing it on every consumer.
As far as I can tell, the only place that monkeypatching is used, is for
interacting with requests. The only place this is directly used by
the client is in
steam.core.CMClient.boostrap_from_webapi, which isonly called on the initial connection. Letting that call be synchronous,
if the user doesn't want to use gevent directly seems reasonable.