ok -- I couldn't let it go, and troubleshooting an awkward bug we have encountered which I could not really figure out (still can't) exactly. But situation is that in datalad project we provide a git-annex special remote which communicates with git-annex via stdin/stdout. Mere import of tqdm lead to something in communication not work out as it should, but only on Debian stretch (testing, with colorama 0.3.7), and worked okish on stable and various ubuntus (colorama <= 0.3.2).... so it might be that difference in behaviour is due to those versions difference but I didn't have time to do all the dance to bisect. Troublshooting further pointed out to colorama.init as the cause of the communication problem.
But is colorama needed only on windows?
or it is useful to be "initialized" on any system?
how useful it is if interface is not interactive?
I just wondered if use of colorama should be conditioned on the system and in general made optional?
ok -- I couldn't let it go, and troubleshooting an awkward bug we have encountered which I could not really figure out (still can't) exactly. But situation is that in datalad project we provide a git-annex special remote which communicates with git-annex via stdin/stdout. Mere import of tqdm lead to something in communication not work out as it should, but only on Debian stretch (testing, with colorama 0.3.7), and worked okish on stable and various ubuntus (colorama <= 0.3.2).... so it might be that difference in behaviour is due to those versions difference but I didn't have time to do all the dance to bisect. Troublshooting further pointed out to
colorama.initas the cause of the communication problem.But is colorama needed only on windows?
or it is useful to be "initialized" on any system?
how useful it is if interface is not interactive?
I just wondered if use of colorama should be conditioned on the system and in general made optional?