You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if the error happens during the GraphQL request the response body is being printed to stdout along with an empty line
Libraries must not print anything to the console because they're being used in other applications and the way these applications treat the stdout/stderr could vary:
User-facing CLIs could use the the stdout to present the data to users and they do it in a way they need it. Having a raw response in the stdout wouldn't be a desirable behavior
Server-side application often use stdout/stderr to stream logs. And logs are often expected to be in a certain format. Unexpectedly formatted log entries can negatively affect log viewers/analyzers
Expected behavior
The library doesn't do raw prints to the stdout. It does the logging using the standard way of logging in Python using logging module
We are closing this issue because it has been inactive for a few months.
This probably means that it is not reproducible or it has been fixed in a newer version.
If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.
If you still encounter this issue with the latest stable version, please reopen using the issue template. You can also contribute directly by submitting a pull request– see the CONTRIBUTING.md file for guidelines
Issue summary
Currently, if the error happens during the GraphQL request the response body is being printed to stdout along with an empty line
Libraries must not print anything to the console because they're being used in other applications and the way these applications treat the stdout/stderr could vary:
Expected behavior
The library doesn't do raw
print
s to the stdout. It does the logging using the standard way of logging in Python usinglogging
moduleActual behavior
The library
print
s raw GraphQL responsesSteps to reproduce the problem
Reduced test case
N/A
Checklist
The text was updated successfully, but these errors were encountered: