Allow to turn off tqdm via environment variables

[faroit]

often I use the same code on my local dev machine and a cluster node. To not mess up the log files I normally turn off tqdm. While this is a simple change in the python code, I think it would actually be more convenient to let tqdm check for environment variables and thereby add some level of system level control over tqdm.

e.g. TQDM=disabled python run.py could quickly disable tqdm in any script.
This should be easy to implement using os.environ.get(). I can compile a PR if you like this proposal

• I have visited the [source website], and in particular
  read the [known issues]
• I have searched through the [issue tracker] for duplicates

[casperdcl]

why not use

from tqdm import tqdm
import os

for x in tqdm(..., disable=os.environ.get("DISABLE_TQDM", False)):
    ...

[faroit]

thats a quick solution, thanks. I would still like the suggestions in #614

[casperdcl]

Thanks for your patience! Just released tqdm==4.66.0 which includes support for env var overrides. I'm using TQDM_MININTERVAL=5 in most of my CI jobs now :)

[jamesbraza]

For those coming across this issue, the tl;dr on env var overrides (e.g. TQDM_MININTERVAL) works is:

1. env var override support #1491 added utils.envwrap, which decorates functions to pull keyword argument overrides from the environment variables matching a prefix (docs)
2. envwrap decorates the main tqdm with the prefix TQDM_ (amongst other places): https://github.com/tqdm/tqdm/blob/v4.66.2/tqdm/std.py#L951-L960

So to apply this knowledge:

1. Go to the docs for tqdm
2. Look up the desired argument name (e.g. mininterval, disable)
3. Match a keyword argument to your environment variable (e.g. mininterval --> TQDM_MININTERVAL)

[timeleft--]

And just to be clear: TQDM_DISABLE=1 does disable TQDM like the issue author originally requested.