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.
-leif
> On Tue, Jul 5, 2016 at 5:27 PM, Dima Pasechnik <dimp...@gmail.com> wrote:
>> some parts of Sage do not work if Sage is installed in a directory with
>> non-ascii characters in its name. And you have that "Téléchargements" there.
>> Rename it to something ascii-only.
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
