Re: [sage-devel] Re: setlocale problem

2013-08-02 Thread Volker Braun
For the record, the future is UTF-8 instead of ISO-8859-1 / Latin-1. Unless you have a need to stick to the old ways its better to use en_GB.utf8 On Friday, August 2, 2013 3:42:16 PM UTC-4, John Cremona wrote: > The diagnosis was correct: I was ssh-ing from my desktop where the set > is our uni

[sage-devel] Re: UTF-8 and old terminals (new startup banner)

2013-08-02 Thread Volker Braun
Its always hard to please everybody, We haven't really reached any consensus, nor does it sound like there is much to be gained by further discussion. So i'll set the ticket to positive review and leave you with Lichtenberg's aphorism: Ich weiss nicht, ob es besser wird, wenn es anders wird. A

Re: [sage-devel] Re: setlocale problem

2013-08-02 Thread John Cremona
The diagnosis was correct: I was ssh-ing from my desktop where the set is our university's official linux desktop and sets everything to en_GB.iso88591 but when you install ubuntu and say your are English-UK it only installs en_GB. Something like that anyway. Then ssh-ing to the new machine forwa

[sage-devel] Re: setlocale problem

2013-08-02 Thread Volker Braun
On Friday, August 2, 2013 2:55:03 PM UTC-4, Keshav Kini wrote: > It's not recommended? Debian seems to recommend it: > https://wiki.debian.org/Locale#SSH_Client > Well its definitely not recommended if your locale is not installed on the remote computer you are logging in to ;-) OpenSSH defau

[sage-devel] Re: setlocale problem

2013-08-02 Thread Keshav Kini
Volker Braun writes: > Are you ssh-ing into the machine or not? And if yes, from where? It > is not recommended to forward the environment by default over ssh but > it can be configured (see SendEnv, AcceptEnv in the ssh > configuration, /etc/ssh/ or ~/.ssh/config) It's not recommended? Debian s

[sage-devel] Re: UTF-8 and old terminals (new startup banner)

2013-08-02 Thread Keshav Kini
William Stein writes: > Also, UTF is clearly the future of strings, having native default > support in modern interpreters, editors, etc., and also being critical > to supporting users who aren't using English. Maybe one day Sage will support something like agda-input-method in Emacs :) -Keshav

Re: [sage-devel] Integer(09) broken

2013-08-02 Thread TB
On 02/08/2013 20:05, Harald Schilly wrote: On Fri, Aug 2, 2013 at 6:52 PM, Robert Bradshaw wrote: A leading 0 means octal in Python ah! thanks! unwitting me wasn't aware of that … h Notice that in Python 3 only the 0o777 (and 0O777) syntax is allowed: http://www.python.org/dev/peps/pep-312

Re: [sage-devel] Integer(09) broken

2013-08-02 Thread Harald Schilly
On Fri, Aug 2, 2013 at 6:52 PM, Robert Bradshaw wrote: > A leading 0 means octal in Python ah! thanks! unwitting me wasn't aware of that … h -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving email

Re: [sage-devel] Integer(09) broken

2013-08-02 Thread Robert Bradshaw
A leading 0 means octal in Python, so 08 and 09 are indeed syntax errors. (That's why file permissions 0777 != file permissions 777.) On Fri, Aug 2, 2013 at 9:48 AM, Harald Schilly wrote: > I don't know the exact cause, first I thought the preparser, but it seems > ok, but things like 09 and 08 a

[sage-devel] Integer(09) broken

2013-08-02 Thread Harald Schilly
I don't know the exact cause, first I thought the preparser, but it seems ok, but things like 09 and 08 are broken, while just 0n with 0<=n<=7 works. Examples: * http://aleph.sagemath.org/?z=eJwrKMrMK1Ew1DawBAAT7AMT&lang=sage * http://aleph.sagemath.org/?z=eJzzzCtJTU8t0jCw1AQAF-oDiQ==&lang=sage

[sage-devel] Re: Benchmark in Sage

2013-08-02 Thread Volker Braun
timeit() repeats the benchmark a number of times and prints the best time. Sometimes the run time is slower because of background processes, and the best time over all loops is a reasonably stable measure of how fast the code really is. The number of loops is just for your information; tests th

[sage-devel] Re: Benchmark in Sage

2013-08-02 Thread Verónica Suaste
Thank's both for your answer! Still I have some questions. Probably I'm not understanding what exactly means the first data: the number of loops and how should I consider this. For example if I get the next output for two different functions that I'm trying to compare: 1 loops, best of 3: 36.4 m

Re: [sage-devel] Re: should bool(x > 0) be False or an exception?

2013-08-02 Thread Volker Braun
I tend to be in favor of the True/False/raise Exception model for testing equality, but has anybody looked into what would be involved to transition the Sage ilbrary? I imagine we would have to adapt a lot of code. On Wednesday, July 31, 2013 5:33:30 AM UTC-4, kro...@uni-math.gwdg.de wrote:

Re: [sage-devel] Re: should bool(x > 0) be False or an exception?

2013-08-02 Thread Jakob Kröker
Dear Eviatar, could you provide some arguments for your choice? By the way, 'Unknown' is not usable for fixing this issue, because a value, that is neither True nor False should not be convertible to a boolean or integer or whatever is accepted by the 'if'-statement, but 'if' seems to accept Unk