Commit 2fd5325
committed
TQDM workaround due to unresponsive maintainer
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`1 parent b3a0999 commit 2fd5325
1 file changed
+15
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
| 37 | + | |
37 | 38 | | |
38 | 39 | | |
39 | 40 | | |
| |||
472 | 473 | | |
473 | 474 | | |
474 | 475 | | |
| 476 | + | |
| 477 | + | |
| 478 | + | |
| 479 | + | |
| 480 | + | |
| 481 | + | |
| 482 | + | |
| 483 | + | |
| 484 | + | |
| 485 | + | |
| 486 | + | |
| 487 | + | |
| 488 | + | |
| 489 | + | |
475 | 490 | | |
476 | 491 | | |
477 | 492 | | |
| |||
0 commit comments