[sage-devel] Re: Logging and optional tests

Hi Jeroen, On 2016-08-18, Jeroen Demeyer wrote: > On 2016-08-18 11:22, Simon King wrote: >> What are you talking about? The current optional Sage package "meataxe" >> is the latest upstream from Aachen. > > I was under the impression that you needed special patches and

[sage-devel] Re: Logging and optional tests

Hi Dima, On 2016-08-18, Dima Pasechnik wrote: > Anyway, I guess it depends upon how much GAP code you have. If its hundreds > of lines it's probably nicer to put them into a file. It is about 1500 lines, currently in three files. Cheers, Simon -- You received this message

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

Recently, in ipython5.0 branch of https://github.com/stakemori/sage-shell-mode, I implemented functions for some of ANSI sequences. (sage-shell-mode handles only ^[[nA, ^[[nB, ^[[nC, ^[[nD, ^[[nH and ^[[nJ) It is not stable enough yet, but it works. I think a similar fix also works for

Re: [sage-devel] Re: error installing top com

On 2016-08-19 04:16, James Khan wrote: Hi! Many thanks for your message and kind help. I am running virtual machine on windows 7 and the sage 7.3 link is not ready yet (the source code is there but not the sage-7.3.ova) so I am stuck with 7.2 for the time being :( I have indeed tried ./sage -i

Re: [sage-devel] Re: error installing top com

Hi! Many thanks for your message and kind help. I am running virtual machine on windows 7 and the sage 7.3 link is not ready yet (the source code is there but not the sage-7.3.ova) so I am stuck with 7.2 for the time being :( I have indeed tried ./sage -i TOPCOM versus "-i topcom" and then also

Re: [sage-devel] Re: ExpressionNice

On Thursday, August 18, 2016 at 5:32:09 AM UTC-7, Bill Page wrote: > > I think that there was no claim that it was unambiguous and therefore > it implies that some ambiguity would be tolerated. But this has > already been argued ad infinitum and apparently that has resulted in > the current

[sage-devel] Re: error installing top com

Hi! Thanks for pointing this out. I am having the same problems! I have the most recent version of SAGE (7.2) and I have tried all the combinations suggested in this thread: TOPCOM, topcom, download the bz2 and plaving in /upstream/ but still no luck. I wonder why this is the case. I get the

[sage-devel] Re: Logging and optional tests

Hi Jeroen, On 2016-08-18, Jeroen Demeyer wrote: > On 2016-08-18 00:02, Simon King wrote: >> Slightly elaborating on my suggestion: Split the code from the old-style >> p_group_cohomology-2.1.6.spkg into four parts, namely >> 1. an optional package "meataxe", which

[sage-devel] Re: __repr__ in sage.interfaces.InterfaceElement called twice

now building... Am Mittwoch, 17. August 2016 20:38:12 UTC+2 schrieb Volker Braun: > > I made https://trac.sagemath.org/ticket/21269 > > > > On Wednesday, August 17, 2016 at 10:04:47 AM UTC+2, Martin R wrote: >> >> While working on the new fricas interface, I noticed that the >> method __repr__

Re: [sage-devel] Re: Logging and optional tests

On 2016-08-18 00:02, Simon King wrote: Slightly elaborating on my suggestion: Split the code from the old-style p_group_cohomology-2.1.6.spkg into four parts, namely 1. an optional package "meataxe", which provides a C library and some executables and which is *not* a Python package. It is

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

Since solving this appears to be tricky, is there a way to undo the ipython-5 thing? (I'd like to keep other things from sage 7.4... -- 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

Re: [sage-devel] Re: Logging and optional tests

On Thursday, August 18, 2016 at 7:37:28 AM UTC+1, Jeroen Demeyer wrote: > > On 2016-08-18 00:02, Simon King wrote: > > Slightly elaborating on my suggestion: Split the code from the old-style > > p_group_cohomology-2.1.6.spkg into four parts, namely > > 1. an optional package "meataxe", which

[sage-devel] Re: error installing top com

James Khan wrote: > Hi! > > Thanks for pointing this out. I am having the same problems! > > I have the most recent version of SAGE (7.2) FWIW, the most recent version is Sage 7.3, released a couple of days ago. There have been changes also to the topcom package IIRC, although the error you

[sage-devel] Re: Logging and optional tests

Hi Dima, On 2016-08-18, Dima Pasechnik wrote: >> Does a concept of "GAP packages" and "Singular packages" exist? If so, >> you should follow recommendations for those kinds of packages to install >> your GAP/Singular code. > > With GAP it is problematic, as updating GAP

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

PS: It would be easy enough to expose the simple-prompt either to the sage command line or have a special sage-embedded commandline entrypoint that starts witout any ANSI sequences. On Thursday, August 18, 2016 at 1:32:18 PM UTC+2, Volker Braun wrote: > > IMHO this is an intentional upstream

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

IMHO this is an intentional upstream change and not a bug. So we'll have to either go with it or fork our own IPython. And I don't want to maintain an IPython fork. On Thursday, August 18, 2016 at 11:08:41 AM UTC+2, Martin R wrote: > > Since solving this appears to be tricky, is there a way to

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

Am Donnerstag, 18. August 2016 13:33:41 UTC+2 schrieb Volker Braun: > > PS: It would be easy enough to expose the simple-prompt either to the sage > command line or have a special sage-embedded commandline entrypoint that > starts witout any ANSI sequences. > > I have absolutely no idea how to

[sage-devel] Re: Logging and optional tests

On Thursday, August 18, 2016 at 12:59:39 PM UTC+1, Simon King wrote: > > Hi Dima, > > On 2016-08-18, Dima Pasechnik wrote: > >> Does a concept of "GAP packages" and "Singular packages" exist? If so, > >> you should follow recommendations for those kinds of packages to >

Re: [sage-devel] Re: Logging and optional tests

On 2016-08-18 11:22, Simon King wrote: What are you talking about? The current optional Sage package "meataxe" is the latest upstream from Aachen. I was under the impression that you needed special patches and that "the latest upstream from Aachen" did not work for you. Anyway, it doesn't

Re: [sage-devel] Re: ExpressionNice

On 18 August 2016 at 01:59, Nils Bruin wrote: > On Wednesday, August 17, 2016 at 3:25:31 PM UTC-7, Bill Page wrote: >> >> >> It turns out that a solution is now "hidden away" in plain sight: >> >> https://trac.sagemath.org/ticket/18640 >> >>

Re: [sage-devel] Re: error installing top com

Hi! Thanks a lot for getting back promptly! Sorry it's an old post; I was just getting desperate and was googling. :) Would you think updating to SAGE 7.3 would help? I don't why TOPCOM is not loading. I am running a windows version, maybe that's a problem? thanks!! On Thu, Aug 18, 2016 at

[sage-devel] Re: error installing top com

James Khan wrote: > Hi! > > Thanks a lot for getting back promptly! Sorry it's an old post; I was > just getting desperate and was googling. :) Would you think updating to > SAGE 7.3 would help? I guess it will, at least give better error messages... ;-) > I don't why TOPCOM is not loading. I

Re: [sage-devel] Re: ExpressionNice

ExpressionNice is a subclass of sage.symbolic.expression.Expression, it seemed therefore that maybe I should be able to do something like: sage: import sage.manifolds.utilities sage: sage.symbolic.expression.Expression = sage.manifolds.utilities.ExpressionNice and expect all my expressions to be

Re: [sage-devel] Re: Logging and optional tests

On 2016-08-18 16:43, Simon King wrote: What do you mean by Singular interface? If I understand correctly, your package has an interface for GAP, Singular and Sage and these are all independent from eachother. I am asking that, if somebody has Singular installed but not GAP and not Sage,

[sage-devel] PlatformKeyboardEvent error in Sage notebook

When I have a Sage notebook in the browser, as I scroll up or down I frequently see the following error on the console: [1:1:0818/131348:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static blink::PlatformEvent::Modifiers

[sage-devel] Re: Logging and optional tests

Hi Jeroen, On 2016-08-18, Jeroen Demeyer wrote: > On 2016-08-18 16:43, Simon King wrote: >> What do you mean by Singular interface? > > If I understand correctly, your package has an interface for GAP, > Singular and Sage and these are all independent from eachother. In

[sage-devel] Re: PlatformKeyboardEvent error in Sage notebook

Thats a chrome bug thats already fixed upstream... On Thursday, August 18, 2016 at 9:01:04 PM UTC+2, cir...@gmail.com wrote: > > When I have a Sage notebook in the browser, as I scroll up or down I > frequently see the following error on the console: > >