[sage-devel] Signal handling

Hello! I'm trying to run Django inside of the Sage python and import the sage libraries. (Idea: "Hey, look, a web server that can find derivatives!") The Django install into my Sage install went fine, but I'm getting an error when trying to import the Sage libraries: http://dpaste.com/1038581

Re: [sage-devel] Errors in doctest on OS X 10.8.2

> > I finally retested using 5.9 Beta 1 and all tests passed. Thank you! > -- 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.co

[sage-devel] Re: skynet

On Thursday, March 28, 2013 6:47:49 PM UTC+1, Volker Braun wrote: > > Clint already has an account on skynet from what he told me earlier... Maybe he just lost his password, private key or whatever he used to authenticate himself. Or maybe there was another issue: "Is there a sage sysadmin agai

[sage-devel] Re: cell server not working well

> > > *Update*: Looking into this more, it appears that some of the changes > that one of us did meant that the script that automatically restarts the > server was pointing to the wrong domain. The result was that the server > was getting restarted every two minutes. That explains a lot. I t

[sage-devel] Re: Annoying inconsistency of type in doctests

We can reach inside IPython and put another formatter in place for "type" and "classobj" objects: sage: type(1) sage.rings.integer.Integer sage: import IPython sage: self=sys.displayhook.shell.display_formatter.formatters[u'text/ plain'] sage: T=[k for k,v in self.type_printers.items() if v is IPy

[sage-devel] Re: cell server not working well

On 3/28/13 1:20 PM, kcrisman wrote: On Thursday, March 28, 2013 2:02:17 PM UTC-4, jason wrote: On 3/28/13 12:55 PM, Dan Drake wrote: > Hello, > > The cell server (sagecell.sagemath.org ) is not working very reliably > right now. One tim

[sage-devel] Re: cell server not working well

On Thursday, March 28, 2013 2:02:17 PM UTC-4, jason wrote: > > On 3/28/13 12:55 PM, Dan Drake wrote: > > Hello, > > > > The cell server (sagecell.sagemath.org) is not working very reliably > > right now. One time it complained about a websocket problem (even though > > I'm using a recent ver

[sage-devel] Re: cell server not working well

On 3/28/13 12:55 PM, Dan Drake wrote: Hello, The cell server (sagecell.sagemath.org) is not working very reliably right now. One time it complained about a websocket problem (even though I'm using a recent version of Firefox); many times when I try to evaluate something, nothing happens. I just

[sage-devel] cell server not working well

Hello, The cell server (sagecell.sagemath.org) is not working very reliably right now. One time it complained about a websocket problem (even though I'm using a recent version of Firefox); many times when I try to evaluate something, nothing happens. I just posted an @interact to a blog, so I hop

[sage-devel] Re: skynet

Clint already has an account on skynet from what he told me earlier... I don't know who (if any) is in charge. On Thursday, March 28, 2013 5:32:45 PM UTC, Jean-Pierre Flori wrote: > > Is anyone in charge of the "skynet" cluster? > > -- You received this message because you are subscribed to t

[sage-devel] skynet

Hi all, Is anyone in charge of the "skynet" cluster? R. Clint Whaley is ready to have a look at the ia64 failure in ATLAS 3.10.1 testsuite, see: https://sourceforge.net/p/math-atlas/support-requests/846/#bfa1 which seems to be the final blocker to #10508 (ok there was no definitive review but l

[sage-devel] Re: Bad latex for elements of SL2Z

The SL2Z object is from the modular stuff with about zero integration with matrix groups, unfortunately. Compare the "matrix group" SL(2,Z): sage: S, T = SL(2,ZZ).gens() sage: latex(S) \left(\begin{array}{rr} 0 & 1 \\ -1 & 0 \end{array}\right) The output comes from the modular SL2Z having no fu

[sage-devel] Substitute expression inside differential equation

Hi Basu! On Tue, Mar 19, 2013 at 01:57:07AM -0700, P Purkayastha wrote: >Hi, > I am trying to remove the deprecation message that pops up when we try >to substitute a variable in a symbolic expression with some value. The >deprecation has been around for about four years.

[sage-devel] Bad latex for elements of SL2Z

This is horrible (and causes nasty things to happen in SageTex): sage: S,T = SL2Z.gens() sage: latex(S) \begin{array}{l} \verb|[|\phantom{\verb!x!}\verb|0|\phantom{\verb!x!}\verb|-1]|\\ \verb|[|\phantom{\verb!x!}\verb|1|\phantom{\verb!xx!}\verb|0]| \end{array} This is much better: sage: latex(S.

[sage-devel] Re: Re: slow arithmetic in number fields

David Roe a écrit : > More documentation is always good, but I would argue that the right > solution is to change the behavior of power series rings to line up with > p-adics. Would there be any difference left between A[[x]] and A[x]/(x^n), then? -- Marc -- You received this message because y

[sage-devel] Re: Annoying inconsistency of type in doctests

+1 for making this consistent. Its a "feature" of the IPython displayhook: sage: sys.displayhook(type(1)) sage.rings.integer.Integer On Thursday, March 28, 2013 9:28:46 AM UTC+1, Simon King wrote: > > In sage-5.8, one gets > sage: type(ZZ) > sage.rings.integer_ring.IntegerRing_class > >

Re: [sage-devel] Re: Annoying inconsistency of type in doctests

I believe that this is a change due to updating IPython: you get different results for type depending on whether you're in an IPython shell or a Python script. I don't know how to fix it though. David On Thu, Mar 28, 2013 at 1:36 AM, Simon King wrote: > Hi Julien, > > On 2013-03-28, Julien Puy

[sage-devel] Re: Annoying inconsistency of type in doctests

Hi Julien, On 2013-03-28, Julien Puydt wrote: > Search for "sage: type" in the sage sources and you'll see that you > should test like this: > > sage: import sage.server.notebook.css as c > sage: type(c.css()) > > > so the test should have the form, even if it's not

Re: [sage-devel] Annoying inconsistency of type in doctests

Le 28/03/2013 09:28, Simon King a écrit : In sage-5.8, one gets sage: type(ZZ) sage.rings.integer_ring.IntegerRing_class Putting this as a doctest into a file testtype.py, one gets sage -t "/home/simon/SAGE/tests/testtype.py" *

[sage-devel] Annoying inconsistency of type in doctests

Hi! In sage-5.8, one gets sage: type(ZZ) sage.rings.integer_ring.IntegerRing_class Putting this as a doctest into a file testtype.py, one gets sage -t "/home/simon/SAGE/tests/testtype.py" ** File "/home/

[sage-devel] Re: [sage-combinat-devel] Re: a problem in the new permutation groups code (and a solution ?)

Hell !!! > No, I didn't propose strings. I meant things like > > sage: (None,None,{None,None},None) > (None, None, set([None]), None) > > Now you can replace None with elements of the group domain. Oh ? Then I still don't get it. I thought that you meant that the input should be s