Casper da Costa-Luis
Casper da Costa-Luis
@dvolgyes I think @KrisThielemans's point was that we want liniting but don't want the casual user to be put off because of it. So my suggestion was to: 1. Add...
I prefer `v` too - some version-parsing tools expect it
Not sure what the use case here is. Why do you want a busy-wait? And why do you want it wrapped by `tqdm`?
Posting old message before it gets lost: upshot of auto-pull checkpoints, we need to - `exp pull && exp apply` - `exp run`: specify an experiment name first time but...
also related: https://github.com/iterative/example-repos-dev/issues/83#issuecomment-1128824098
Not sure I understand correctly but is this about parameterising tests randomly? Wouldn't https://github.com/pytest-dev/pytest-randomly integrate better with the current https://github.com/tqdm/tqdm/tree/master/tests?
Hmm not too sure. Can you post a minimal code example? I can run the StackOverflow answer you posted to 100% consistently. Also check out e.g. [`tqdm.contrib.concurrent.process_map`](https://tqdm.github.io/docs/contrib.concurrent/#process_map)
Hmm there looks like there's some sort of deadlock caused by `pool.join()` and perhaps `tqdm.tqdm.close()` or similar. This works though: ```python from tqdm import trange from tqdm.contrib.concurrent import process_map from...
`local`, `pushed`, `synced`?
Can this be closed? ```bash pip install nbdime echo '```diff' >> report.md nbdiff >> report.md echo '```' >> report.md cml send-comment report.md ``` Not sure if @iterative/studio wants to render...