How do you feel about ramathenedit <| sep |> Well you can always take part in our 5 v 5 tournaments for prizes and Coins money . But I hear you , we just need to continue building our playerbase before we think about adding more queues that split them up . <| sep |> Not true , Welfare means Welfare . Welfare is just a slang for government granted cash benefits to poor people , but it still means welfare . <| sep |> Those Voidfang Vestments Xur is selling are a pretty decent stat roll 97 % max roll . <| sep |> This behavior is the correct one though . Theoretically URL , HTTP , email , all have specified encoding , the encoding is USASCIIActually , HTTP specifies ISO 88591 as the encoding for headers . In practice , UTF 8 is used a lot . According to the various standards , email may be encoded , amongst others , as 7 bit i . e . ASCII or 8 bit could be anything . Domain names may be a subset of ASCII , but URLs are not . Do I make my URLs ASCII ? Sure . But it ' s not just my own URLs my code has to work with . but that ' s Linux ' s fuck up not Python ' sIndeed . But it is what it is . This is the world we live in , and I ' d rather have a language that works in it than one that dies in flames and points the finger elsewhere . it will use whatever encoding you specified in LANGLCCTYPE . Except they aren ' t always set . cron , initd , launchd etc . have empty environments . Telling an OS X user they need to dick around in Terminal to get your app to run isn ' t a tenable position . What ' s more , even if you have a valid LANG , if you ssh into a box that doesn ' t support that locale , Py 3 dies in flames . Say , your machine is frFR . UTF 8 but the server is Englishonly . So in the end it ' s cleaner , easier and nicerAnd it dies in flames in some pretty common scenarios . The bottom line is that while Py 3 does The Right Thing , a hell of a lot of other things don ' t . Pointing the finger at them as the reason that Py 3 doesn ' t work with them doesn ' t help me write a working program . command line support is just fine , and you can interact both through bytes and with Unicode , depending on what you choseIt ' s mostly possible . But it ' s easier to get correct behaviour with Py 2 because its text model is the POSIX text model . Frankly , it ' s easier to decode the things you need to decode in Py 2 than it is to undo Py 3 ' s automatic decoding of bytes that shouldn ' t be decoded . I had some issues with Click , but forgot what they were . Perhaps that it refuses to run under Py 3 if it can ' t identify the encoding Py 3 is using in order to unwind Py 3 ' s decoding magic ? If you want to use filename that is in bytes , you simply pass a bytes object to openI love how people like you always assume that I must not know these things .