Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Ipython 5 has now a comman-line switch "ipython --simple-prompt" that disables all escape sequences, but also disables prompt customizations. So instead of sage: its then always In[] / Out[]. I didn't find a way to turn of all ansi sequences while still changing the prompt to "sage:". On

[sage-devel] Re: checkout from trac

IMHO you could just as well use plain git (unless you need to deal with heaps of Sage trac tickets or are not comfortable using git in general...) http://doc.sagemath.org/html/en/developer/manual_git.html#git-the-hard-way On Saturday, August 13, 2016 at 5:07:06 PM UTC+1, Bill Page wrote: > > It

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

I tried %config SageTerminalInteractiveShell.simple_prompt=True in a running session inside Emacs, but it didn’t help. Perhaps it has to be done at the command line? -Ivan > On Aug 14, 2016, at 1:54 AM, Volker Braun wrote: > > Ipython 5 has now a comman-line switch

[sage-devel] Re: patchbot.sagemath.org down?

Happy to hear that you care about the patchbot. Maintenance is currently being done (slowly). It will hopefully be resurrected soon. Frédéric Le dimanche 14 août 2016 18:17:12 UTC+2, Eric Gourgoulhon a écrit : > > Hi, > > Since yesterday (at least), it seems that patchbot.sagemath.org is >

Re: [sage-devel] py3: what to do with cmp ?

On 2016-08-14 14:41, Frédéric Chapoton wrote: Otherwise, one will have to get rid /by hand/ of all the `__cmp__` methods everywhere, that will become obsolete in python3. Don't confuse the cmp() function with __cmp__() methods! Getting rid of cmp() and getting rid of __cmp__() are a priori

[sage-devel] py3: what to do with cmp ?

As an intermediate step in our long way to python3, I would like to be able to compile all the .pyx files in py3. Except for #21246 (please review), the big remaining problem preventing to reach this goal is the removal of the builtin "cmp" in py3. One solution would be to have our own "cmp"

Re: [sage-devel] py3: what to do with cmp ?

Getting rid of __cmp__ would be the cleaner way but a simple grep on $SAGE_ROOT/src gives 915 occurrences of __cmp__, 624 of which are definitions. Is there any way we can automate the process? S. * Frédéric Chapoton [2016-08-14 05:41:01]: >As an intermediate step in

Re: [sage-devel] Re: py3: what to do with cmp ?

Really weird, his is what I have: $ cd $SAGE_ROOT/src $ grep __cmp__ **/*.py* | grep def | wc 6242538 48212 $ grep __cmp__ **/*.py* | wc 9154020 76837 (I am running zsh so **/*.py* is expanded to any file under $SAGE_ROOT/src whose extension begin by py) S. * leif

[sage-devel] Re: py3: what to do with cmp ?

VulK wrote: > Really weird, his is what I have: > > $ cd $SAGE_ROOT/src > $ grep __cmp__ **/*.py* | grep def | wc > 6242538 48212 > $ grep __cmp__ **/*.py* | wc > 9154020 76837 > > (I am running zsh so **/*.py* is expanded to any file under $SAGE_ROOT/src > whose extension

[sage-devel] Should @experimental be used on a completely new module in Sage

Hi sage-devel, As a huge part of Arpit Merchant's GSoC project on Gabidulin codes, we've been working on Xavier Caruso's old patch implementing skew polynomial rings, #13215. While everyone involved has considered the code and math carefully, it is my opinion that the design could still be

[sage-devel] Re: py3: what to do with cmp ?

leif wrote: > VulK wrote: >> Really weird, his is what I have: >> >> $ cd $SAGE_ROOT/src >> $ grep __cmp__ **/*.py* | grep def | wc >> 6242538 48212 >> $ grep __cmp__ **/*.py* | wc >> 9154020 76837 >> >> (I am running zsh so **/*.py* is expanded to any file under

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Hi, On my machine, Ivan's workaround also does not help: I get exactly the same behaviour as Martin R. I run Emacs 24.5.1 on Arch Linux 4.6.3-1, x86_64. See also this depressing post on Emacs Stack Exchange: http://emacs.stackexchange.com/questions/24453/weird-shell-output-when-using-ipython-5

[sage-devel] Re: Should @experimental be used on a completely new module in Sage

Johan S. H. Rosenkilde wrote: > Hi sage-devel, > > As a huge part of Arpit Merchant's GSoC project on Gabidulin codes, > we've been working on Xavier Caruso's old patch implementing skew > polynomial rings, #13215. > > While everyone involved has considered the code and math carefully, it > is

[sage-devel] Re: py3: what to do with cmp ?

VulK wrote: > Getting rid of __cmp__ would be the cleaner way but a simple grep on > $SAGE_ROOT/src gives 915 occurrences of __cmp__, 624 of which are > definitions. Is there any way we can automate the process? > S. I have to admit I fail to see the problem (perhaps Frédéric could elaborate a

[sage-devel] sage server and test_notebook

Hi, I was trying to get a sage server running on a computer at work and I kept finding that it would not connect. I then started debugging and ran into further issues. When I execute the documentation http://doc.sagemath.org/html/en/reference/notebook/sagenb/notebook/notebook_object.html

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

at least on my other computer, running GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.9) of 2015-03-21 on kissel, modified by Debian this does not help. However, on this computer I don't even get to the (weird) sage prompt, unless I hit C-g. I evaluated the two definitions you

[sage-devel] Re: Error building after checking out old version.

Hi, Thanks for the advice. At some point I'd hope to do something along the lines discussed in this thread. https://groups.google.com/forum/#!topic/sage-devel/9lHpGgG3nsI But more and more I'm figuring out those plans are going to have to be longer term than I initially, perhaps naively,

[sage-devel] Re: sage_mode for emacs has display problem in sage 7.4 beta0

Ivan Andrus wrote: > It looks like ipython is printing invalid (or at least unknown to Emacs) > > I got it to ignore them by setting > > (setq ansi-color-drop-regexp > " > \\[\\([ABCDsuK]\\|[12][JK]\\|=[0-9]+[hI]\\|[0-9;]*[HfDnC]\\|\\?[0-9]+[hl]\\|J\\ > )") > > There is also a bug in my

[sage-devel] Re: py3: what to do with cmp ?

leif wrote: > VulK wrote: >> Getting rid of __cmp__ would be the cleaner way but a simple grep on >> $SAGE_ROOT/src gives 915 occurrences of __cmp__, 624 of which are >> definitions. ? I'm getting 339 definitions in 249 files. (That's for 7.3.beta9, but shouldn't differ that much.) -leif >>

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

On Aug 14, 2016 11:26 AM, "'Martin R' via sage-devel" < sage-devel@googlegroups.com> wrote: > > Can't we undo the ipython 5 thing? It's a major nuisance on the command line, too. > +1 I find the new coloration in the Sage command line in the beta release quite extreme and nearly unreadable in

[sage-devel] patchbot.sagemath.org down?

Hi, Since yesterday (at least), it seems that patchbot.sagemath.org is unreachable. Eric. -- 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] git trac error

Hi, all, I admit to being a total novice in the New World of Sage development (post-git). Using OS X, 10.11.6, I attempted just now to “git” the code from a trac ticket (which has every indication of being more-or-less up-to-date, git-wise), and got this in response (on a freshly-built 7.3):

Re: [sage-devel] Re: git trac error

You need the newest git-trac version, presumably you checked out the repo somewhere. Find it and run "git pull (in the git-trac repo folder) On Sunday, August 14, 2016 at 10:51:36 PM UTC+2, Justin C. Walker wrote: > > > On Aug 14, 2016, at 13:44 , Dima Pasechnik wrote: > > > > > > > On

Re: [sage-devel] git trac error

> On Aug 14, 2016, at 14:06 , Volker Braun wrote: > > You need the newest git-trac version, presumably you checked out the repo > somewhere. Find it and run "git pull (in the git-trac repo folder) Thanks for that; the updated git-trac did better. Then I ran into this,

[sage-devel] Re: Should @experimental be used on a completely new module in Sage

For the record, I am that reviewer. > As a huge part of Arpit Merchant's GSoC project on Gabidulin codes, > > we've been working on Xavier Caruso's old patch implementing skew > > polynomial rings, #13215. > > > > While everyone involved has considered the code and math carefully, it > > is

[sage-devel] Re: git trac error

On Sunday, August 14, 2016 at 9:17:27 PM UTC+1, Justin C. Walker wrote: > > Hi, all, > > I admit to being a total novice in the New World of Sage development > (post-git). > post-git??? Hopefully not... You know how to use git, right? Then:

Re: [sage-devel] Re: py3: what to do with cmp ?

you got me: I was including $SAGE_ROOT/src/build/ now the numbers agree S. * leif [2016-08-14 16:55:23]: > leif wrote: > > VulK wrote: > >> Really weird, his is what I have: > >> > >> $ cd $SAGE_ROOT/src > >> $ grep __cmp__ **/*.py* | grep def | wc > >> 6242538

Re: [sage-devel] Re: git trac error

On Aug 14, 2016, at 13:44 , Dima Pasechnik wrote: > > > On Sunday, August 14, 2016 at 9:17:27 PM UTC+1, Justin C. Walker wrote: >> >> Hi, all, >> >> I admit to being a total novice in the New World of Sage development >> (post-git). >> > post-git??? Hopefully not... Well, yeah;

[sage-devel] Re: git trac error

Justin C. Walker wrote: > >> On Aug 14, 2016, at 14:06 , Volker Braun wrote: >> >> You need the newest git-trac version, presumably you checked out the repo >> somewhere. Find it and run "git pull (in the git-trac repo folder) > > Thanks for that; the updated git-trac

[sage-devel] Re: Should @experimental be used on a completely new module in Sage

Travis Scrimshaw wrote: > For the record, I am that reviewer. > > > As a huge part of Arpit Merchant's GSoC project on Gabidulin codes, > > we've been working on Xavier Caruso's old patch implementing skew > > polynomial rings, #13215. > > > > While everyone involved has

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

> On Aug 14, 2016, at 11:28 AM, Johan S. H. Rosenkilde > wrote: > > Hi, > > On my machine, Ivan's workaround also does not help: I get exactly the > same behaviour as Martin R. I run Emacs 24.5.1 on Arch Linux 4.6.3-1, > x86_64. > > See also this depressing post on