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
Thanks for making this available, it wraps up multiprocessing and threading nicely for my use case!
I'm using this to pull data from a server making requests using the requests package. It works, but the I think the requests.get calls I'm making are printing debug statements for each loop. I'm using atpbar as well and this debug statements are causing the progress bars to be re-printed alternating with the requests debug statements rather than updating.
I tried following the example showing how to use logging and tried that with level=logging.DEBUG, but so far that hasn't prevented the debug statements from being printed. Quite possibly because I've implemented it wrong.
I just tried turning off the logging by doing the following, which worked.
Any suggestions on a better option? I would think the logging example would work if it was re-directing the requests debug statements to a file, so maybe I just have an issue there. Thanks!
The text was updated successfully, but these errors were encountered:
If you check out atpbar from the HEAD of the main branch in the GitHub repo, the stdout and stderr will be printed above the progress bars. Hopefully, that will solve the problem.
Thanks for making this available, it wraps up multiprocessing and threading nicely for my use case!
I'm using this to pull data from a server making requests using the requests package. It works, but the I think the
requests.get
calls I'm making are printing debug statements for each loop. I'm usingatpbar
as well and this debug statements are causing the progress bars to be re-printed alternating with the requests debug statements rather than updating.I tried following the example showing how to use logging and tried that with
level=logging.DEBUG
, but so far that hasn't prevented the debug statements from being printed. Quite possibly because I've implemented it wrong.I just tried turning off the logging by doing the following, which worked.
Any suggestions on a better option? I would think the logging example would work if it was re-directing the requests debug statements to a file, so maybe I just have an issue there. Thanks!
The text was updated successfully, but these errors were encountered: