Op woensdag 18 september 2013 10:22:04 UTC+1 schreef Jeroen Demeyer:
On 2013-09-18 07:20, Dima Pasechnik wrote:
accoring to http://www.python.org/dev/peps/pep-0263/
$SAGE_LOCAL/bin/hg might benefit from the 2nd line saying
# -*- coding: latin-1 -*-
(or # -*- coding: utf-8 -*-) ?
PEP 0263 says explicitly that the encoding magic can occur either on the
first or on the second line, presumably for cases like this, so it looks
like it is worth trying.
(If it already tries to decode the first line before looking at the second
line to see if it specifies an encoding,
Hi,
Jan Groenewald wrote:
It might be the é in your path, though \xc3 is something else:
In [1]: print u'\xc3'
Ã
0xC3 is the first byte of the UTF-8 encoding of 'é'.
--
Marc
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from
Hi,
I think I also had similar problems because of accented letters in my
building path.
I don't know if that would be easy to fix, but you can always build Sage
lesewhere and then move it back where you want to store it even if that
includes accented letters.
Best,
JP
On Wednesday,
On 2013-09-18 07:20, Dima Pasechnik wrote:
accoring to http://www.python.org/dev/peps/pep-0263/
$SAGE_LOCAL/bin/hg might benefit from the 2nd line saying
# -*- coding: latin-1 -*-
(or # -*- coding: utf-8 -*-) ?
That wouldn't help since the offending character is on the *first* line,
before
On 2013-09-17, ti tims tit...@gmail.com wrote:
Hi all @sage
I do not succeed in compiling sage 5.11 on debian testing. here is the output
copying build/scripts-2.7/hg -
/home/tm202135/Téléchargements/sage-5.11/local/bin
changing mode of
