-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cuvner is incompatible with ansicolors 1.1.6 #7
Comments
Hmm, looks like https://github.com/jonathaneunice/colors/blob/master/colors/colors.py#L109 should be a unicode literal to work properly on Python2? |
Seems plausible - but the docstring for |
otoh, reading the |
Merely changing that string to a unicode literal will break usage like |
Looks to me like this was unintended fallout from this commit: jonathaneunice/colors@67dd97f#diff-3358adf77afc6138373d66e0d18cd3b6L101 ...because: |
"Yes" to your last comment. Hmm... I'll file an issue on colors and see what we come up with? But this will just not work, ever: |
Hmm, maybe @jonathaneunice can comment here? It seems colors isn't using the github bugtracker (and I don't see any other thing being used). |
I guess for now I can pin cuvner to 1.0.2 |
Okay, I did that and released 17.3.0 |
This goes away when I downgrade ansicolors to 1.0.2.
The text was updated successfully, but these errors were encountered: