#beets

hmm.. got it down to 1 error and 7 failures .. but broke python 2.7..

sampsyo, i think I get personally confused because I can't tell why it's ok for click to fail on ascii but not latin1 stuff

it must only be because of anglocentric concerns

or eurocentric rather

jrobeson: Yeah, isn't that confusing? I don't quite get that either

Maybe Armin's just saying that ASCII is the most common misconfiguration, and others might actually be intended for some reason?

i can't imagine how that's the case

based on the actual code that is

because it just returns if it's not ascii

but really the question for us is.. outside of click.. is a non utf8 locale ever ok on linux

and how common is it

most of the distros are now including a C.utf8 locale

in the end though, we're still gonna do our best on windows, so i guess it doesn't matter too much

sampsyo, we could uncover more bugs by adding say LANG=de_DE to our build matrix .. i discovered that :(

i tried LANG=ja_JA, but that failed even earlier

Really? Does that affect the encoding that Python chooses?

which one?