Add initialization counter

[Gaming32]

Resolves #205.

[tartley]

Hey. FYI, Yesterday I created a PR to test releases before we push them to PyPI. When that is merged, I'll be more confident about resuming merges and releases. I'll try to look at this PR soon. Thank you for creating it!

The above is cut-and-paste to everyone. To you especially: thank you, that is a rubbish bug, and I'm really happy to see a fix for it!

[Erotemic]

Getting this fixed would help my use cases. Alternatively, if I had a way of knowing if colorama was ever initialized (even if it was deinitialized later), that would be enough for me. Currently I'm testing if colorama.initialise.atexit_done is Falsy, which works, but may not be the most stable test for this.

[Gaming32]

@tartley Any updates on this?

[tartley]

No updates currently, no.

But! For various reasons, I plan to give Colorama some love soon.

[tartley]

Is this a dupe of #236 ?

[tartley]

An alternative approach to these problems has been suggested. Instead of modifying the poorly thought out interface and behavior of the original 'init' function, which is nontrivial and might be relied upon by existing programs, a proposal has been made by njsmith to add a new function, in parallel with init, which behaves more sanely, and hopefully will address your issues with it.

See njsmith's final comment here ("I would like to sneak one more feature in...") before I merged that PR. The intention is to merge that relatively trivial PR, then make a release.