-
-
Notifications
You must be signed in to change notification settings - Fork 396
TQDM workaround due to unresponsive maintainer #1363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
tqdm has an incorrect detection of ZMQInteractiveShell when launch via a scheduler that bypass IPKernelApp. Think of JupyterHub cluster spawners and co. As of end of Feb 2025, the maintainer has been unresponsive for 5 months, to our fix, so we implement a workaround. I don't like it but we have few other choices. See `https://github.com/tqdm/tqdm/pull/1628`
krassowski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see that even once the maintainer of tqdm has some more time, they can take a while to respone as there is a a few upstream PRs related to improving notebook autodetection:
Not sure if we can provide any feedback on the other PRs, but if there are any thoughts we could share to help with review upstream, this might help to move it forward.
|
To backport. |
Co-authored-by: Min RK <[email protected]>
|
I hope this will get merged one day. |
Co-authored-by: Min RK <[email protected]>
tqdmhas an incorrect detection of ZMQInteractiveShell when launch via a scheduler that bypass IPKernelApp. Think of JupyterHub cluster spawners and co.As of end of Feb 2025, the maintainer has been unresponsive for 5 months, to our fix, so we implement a workaround. I don't like it but we have few other choices.
See tqdm/tqdm#1628