William Stein wrote:
> On Tue, Jul 5, 2016 at 10:37 AM, leif <not.rea...@online.de> 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.

I'm absolutely not against fixing that /where we can/, I'm just saying
we can hardly "fix" each and every package Sage includes, and we sadly
have to live with that, at least for a while.  (Though as a disciple of
Unix, I think putting spaces into filenames and especially folder names
is a bad idea in the first place.  We should just give an /appropriate/
error message, to the right time, i.e. asap.  In this case, Sage's
top-level 'configure' should bail out until we support "non-ASCII"
characters in the pathname of a Sage source tree.  Having a Sage
installation reside in such a folder is by the way a related, but
different problem, as long as you don't rebuild packages at least.)

I was also especially referring to "[7-bit?] ASCII characters", where
rather [a-zA-Z0-9_] was meant.  (Python btw. also implies restrictions
on module-, package- and hence also filenames AFAIK.)


-leif


-- 
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.

Reply via email to