On Tue, Jul 5, 2016 at 10:37 AM, leif <[email protected]> wrote: > Erik Bray wrote: >> That could and probably should be fixed though. In this case just >> changing decode('ascii') to decode('latin1') will go a long way (will >> result in mojibake for some code pages, but at least won't crash). >> Better still is to try utf-8 first and fall back on latin-1 if that >> fails. > > We do not even support spaces in the pathname (a common problem for > MacOS X and Windoze users), since that already breaks a couple of > upstream packages.
We shouldn't actively discourage people from improving the quality of Sage. Pointing out that Sage is broken in other ways is not a compelling argument against fixing a build system bug. -- William -- William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
