Casper da Costa-Luis
Casper da Costa-Luis
EOL tagged: will only merge if there are new features introduced here that cannot be implemented in the old framework.
While everything you say is (arguably) correct, there is still no reason to merge this. If a new useful config option is released which *only* works in `setup.cfg` and not...
@KOLANICH thanks for the contributions - please leave at least one issue/PR open though (#721 or #733) as a place for discussion. This PR will probably be merged at some...
sure but will that always be the case?
I was just working on this! going to merge into this PR... thanks, Stephen. On 4 August 2016 at 22:58, Stephen L. [email protected] wrote: > Not the most urgent PR,...
Might merge in #227 (which is simple) and put this PR into a submodule as suggested there as it's quite large
@flying-sheep could you fix the unit tests?
#402 may have been invalid, but this PR could still be useful for other purposes. Why do you think it's invalid?
There used to be `tqdm.closed` but this was found to be redundant since whenever it was checked it's value was equal to `tqdm.disable`... which you could use instead. async usage...
v1.0 was slooooooow. easy to beat