10:53 <mapreri> rbasak: besides that I can't see why anybody would want to limit its filesystem to ASCII-only (which, btw, would be a purely artificial limitation I can't even think where to set), reading it as UTF-8 would Just Work.
10:57 <mapreri> Besides, I'm not convinced that I should be setting LANG=C.UTF-8 anywhere to just open a file that happens to have a non- ASCII filename. 10:57 <mapreri> and yes, setting LANG=C.UTF-8 would workaround the bug, but it's very much not the fix here. 10:58 <mapreri> (i.e. it worked before, it works after with the new upstream, it just doesn't work in-between…) 12:49 <rbasak> mapreri: would setting LANG correctly be a bug workaround, or would it be fixing the root cause? Do you know how it is that your system came to have LANG be unset? 12:49 <rbasak> mapreri: I'm concerned because the patch introduces a behaviour change, and some users may have problems with that in a way I can't necessarily predict. 12:50 <rbasak> mapreri: on the other hand, if you're impacted (I think by having a misconfigured server in the first place), then you can fix the behaviour on your own server without having something forcibly pushed out to everyone else. 12:51 <rbasak> mapreri: if you're concerned about doing it globally, you could arrange to set LANG just for that process even. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694261 Title: Crashes with UnicodeDecodeError when trying to handle paths with non- ascii chars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-werkzeug/+bug/1694261/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
