Re: [sage-devel] Re: Upper case letters in Sage Notebook

2014-07-22 Thread v_2e
On Tue, 22 Jul 2014 13:59:35 -0700 (PDT) Emmanuel Charpentier wrote: > The error message below, however, > *hints at the problem in the lines that read : > "line 522, in _user raise LookupError("no user '{}'".format > (username)) exceptions.LookupError: no user 'V_2e' " > Sure it does, but the

[sage-devel] Re: Upper case letters in Sage Notebook

2014-07-22 Thread Emmanuel Charpentier
See below. Le mardi 22 juillet 2014 19:31:49 UTC+2, v_...@ukr.net a écrit : > > Hello! > Today one of my students told me about the problems he experiences > trying to login into Sage Notebook server. In short, the problem was > that he entered his login name with the first letter in upper c

[sage-devel] Re: weird integral behavior

2014-07-22 Thread Emmanuel Charpentier
See answer in text. Le samedi 19 juillet 2014 18:25:42 UTC+2, Anne Schilling a écrit : > > Hi! > > [ Bandwidth savings ] > > Pulling out e^{2\pi i x} to simplify the integral to a one dimensional > integral, > ??? Again, I can't follow you. Care to explain ? > Sage can solve this numerica

[sage-devel] Re: Comparison between str and sage.rings.integer.Integer depends on whether doctest called directly or via Makefile

2014-07-22 Thread Volker Braun
There is no coercion from string and Integer to a common structure. That should be obvious, but we can also check it explicitly: sage: cm = get_coercion_model() sage: cm.explain('i', ZZ(0), operator.eq) Left operand is not Sage element, will try _sage_. Unknown result parent. Hence the compariso

[sage-devel] Re: Comparison between str and sage.rings.integer.Integer depends on whether doctest called directly or via Makefile

2014-07-22 Thread Nils Bruin
On Tuesday, July 22, 2014 11:51:29 AM UTC-7, Clemens Heuberger wrote: > > > May I ask on which system? > Fedora 19 x86_64. I tried your makefile trick and I got consistent results, so I haven't been able to nudge sage or python into the comparison behaviour you described (for any type, really).

[sage-devel] Re: Comparison between str and sage.rings.integer.Integer depends on whether doctest called directly or via Makefile

2014-07-22 Thread Clemens Heuberger
Am 2014-07-22 20:34, schrieb Nils Bruin: > Would you be working on a 32-bit system by any chance? no, 64-bit system. > Is the behaviour reproducible on other systems? > > Not on my 64 bit machine. May I ask on which system? > > > This problem turned up when trying to find out why Vo

[sage-devel] Re: Comparison between str and sage.rings.integer.Integer depends on whether doctest called directly or via Makefile

2014-07-22 Thread Nils Bruin
On Tuesday, July 22, 2014 9:57:13 AM UTC-7, Clemens Heuberger wrote: > > Does that simply mean that cmp(str, sage.rings.integer.Integer) is random? > My guess is that it would be. However, I have not found a type on my system that compares as less than str and I haven't found a type that has id(

[sage-devel] Upper case letters in Sage Notebook

2014-07-22 Thread v_2e
Hello! Today one of my students told me about the problems he experiences trying to login into Sage Notebook server. In short, the problem was that he entered his login name with the first letter in upper case. I was surprised that Notebook distinguishes between the names with upper case and

[sage-devel] Comparison between str and sage.rings.integer.Integer depends on whether doctest called directly or via Makefile

2014-07-22 Thread Clemens Heuberger
Can anyone help me understanding the following behaviour: A doctest (0 < 'I'; see below) passes when called directly and fails when called via a Makefile, reproduced under sage 6.3.beta6, 6.2, 5.10 (running Linux Mint). As pointed out in https://groups.google.com/d/topic/sage-support/KNSz

Re: [sage-devel] Re: flint revert_series

2014-07-22 Thread Jonas Jermann
On 22.07.2014 14:42, Fredrik Johansson wrote:> On Tue, Jul 22, 2014 at > The reversion of t - t^3 + O(t^5) to length n = 5 should be t + t^3 + > O(t^5). This is what I get when I call flint directly from a C > program. Are you getting something different? I meant to write revert_series(6) which d

[sage-devel] Re: speaking spanish or catalan ?

2014-07-22 Thread mmarco
The author is south american? There are several expressions that sound funny to people from Spain. Even there are some that i am not sure they are correct. El martes, 22 de julio de 2014 15:43:01 UTC+2, Frédéric Chapoton escribió: > > Hello, > > is there any spanish (native) speaker there, to h

[sage-devel] speaking spanish or catalan ?

2014-07-22 Thread Frédéric Chapoton
Hello, is there any spanish (native) speaker there, to have a quick look at http://trac.sagemath.org/ticket/7192 that needs review ? and maybe a catalan (native) speaker to look at http://trac.sagemath.org/ticket/12847 ? Thanks, Frederic -- You received this message because you are subscrib

Re: [sage-devel] Re: flint revert_series

2014-07-22 Thread Jean-Pierre Flori
On Tuesday, July 22, 2014 2:05:30 PM UTC+2, Jonas Jermann wrote: > > Hi > > On 21.07.2014 13:10, Fredrik Johansson wrote: > > On Mon, Jul 21, 2014 at 7:37 AM, Jonas Jermann > wrote: > >> I agree, but somehow the "flint import" details are slightly different. > >> I also saw a different name

Re: [sage-devel] Re: flint revert_series

2014-07-22 Thread Fredrik Johansson
On Tue, Jul 22, 2014 at 9:05 PM, Jonas Jermann wrote: > Hi > > > On 21.07.2014 13:10, Fredrik Johansson wrote: >> >> On Mon, Jul 21, 2014 at 7:37 AM, Jonas Jermann >> wrote: >>> >>> I agree, but somehow the "flint import" details are slightly different. >>> I also saw a different name somewhere,

Re: [sage-devel] Re: flint revert_series

2014-07-22 Thread Jonas Jermann
Hi On 21.07.2014 13:10, Fredrik Johansson wrote: On Mon, Jul 21, 2014 at 7:37 AM, Jonas Jermann wrote: I agree, but somehow the "flint import" details are slightly different. I also saw a different name somewhere, "reverse_series". So I was not sure how to exactly import it for nmod. I would a

Re: [sage-devel] Re: Solving rational inequality should give simplified result

2014-07-22 Thread Robert Pollak
I wrote that qepcad cannot deal with terms like '-6 != 0'. This shows as follows: sage: qepcad(-6 != 0, vars='(x)') --- ValueErrorTraceback (most recent call last) in () > 1 qepcad(-Integ

[sage-devel] Re: Solving rational inequality should give simplified result

2014-07-22 Thread Dima Pasechnik
On 2014-07-22, Robert Pollak wrote: > Am 22.07.2014 10:29, schrieb Dima Pasechnik: >> perhaps a newer qepcad can deal with more things (Sage's qepcad 1.50 >> is quite outdated by now). Care to make an update of the corresponding >> spkg? > > I have been thinking about it. > > As a first step I hav

Re: [sage-devel] Re: Solving rational inequality should give simplified result

2014-07-22 Thread Robert Pollak
Am 22.07.2014 10:29, schrieb Dima Pasechnik: > perhaps a newer qepcad can deal with more things (Sage's qepcad 1.50 > is quite outdated by now). Care to make an update of the corresponding > spkg? I have been thinking about it. As a first step I have built qepcad-B-1.69 and its dependency, the cu

[sage-devel] Re: Solving rational inequality should give simplified result

2014-07-22 Thread Dima Pasechnik
On 2014-07-18, Robert Pollak wrote: > > On Monday, July 1, 2013 11:37:02 AM UTC+2, I wrote: >> >> solve(abs((x-1)/(x-5)) <= 1/3, x) >> > [...] >> The main issue is that the result should be >> >> [[-1 <= x, x <= 2]] >> > > I have found a way to get this! A little term massaging gives me the

[sage-devel] Re: Build error in Sage-6.2: pynac-0.3.2

2014-07-22 Thread Jean-Pierre Flori
Hey Stephen, I'll take this occasion to ask you whether all patches needed to build Sage on FreeBSD are currently submitted on our trac? If so, I might update my FreeBSD vms, try them and review them. It would be very nice to be able to build Sage on FreeBSD from scratch. IIRC at some point I cou

[sage-devel] Re: Build error in Sage-6.2: pynac-0.3.2

2014-07-22 Thread Dima Pasechnik
On 2014-07-21, Montgomery-Smith, Stephen wrote: > Hey people, > > FreeBSD people do like to build their ports as root. The problem > described below could be easily fixed by simply removing the group write > permissions of all the files in the tarball upstream/pynac-0.3.2.tar.bz2. > > It's not su