[sage-devel] Polyhedron.vertices() function call behaviour

I have recently created a Polyhedron Q that corresponts to the cuts of a graph. Once I have Q, I created a list of vectors of its vertices as follows: V=[s.vector() for s in Q.vertices()] Now I create a copy of V W= copy(V) Then I change the 6th co-ordinate of each vector in W as follows

[sage-devel] Re: bug: factoring symbolic expressions containing exponentials

Probably best to revert #23835 then, if you insist on the blocker assessment. https://trac.sagemath.org/ticket/23835 Regards, On Wednesday, April 10, 2019 at 9:30:42 PM UTC+2, Bill Page wrote: > > sage: sage.version.version > '8.6' > sage: ex=exp(2*x)+exp(-2*x); ex > e^(2*x) + e^(-2*x) >

Re: [sage-devel] Re: bug: factoring symbolic expressions containing exponentials

Le mercredi 10 avril 2019 23:37:53 UTC+2, Bill Page a écrit : > > On Wed, Apr 10, 2019 at 5:28 PM rjf > > wrote: > > > > > > I suppose this is a Sage bug; Maxima doesn't have a problem with > > its factor program. > > > > Indeed. > > This bug has been reported as

Re: [sage-devel] Build fails: Sage 8.7 on Centos 6.10 x64

yep done - another collegeue had one on our network I was able to get to -- version 6.4.0 And the straight "make" command is building Sage -- without building its own. thanks On Wednesday, April 10, 2019 at 5:44:25 PM UTC-4, Dima Pasechnik wrote: > > On Wed, Apr 10, 2019 at 11:37 PM

Re: [sage-devel] Build fails: Sage 8.7 on Centos 6.10 x64

On Wed, Apr 10, 2019 at 11:37 PM richr410 via sage-devel wrote: > > oh easy - well... > 1) the installed vendor gcc is 4.4.7 OK, this explains. 4.4.7 is way too old. Any chance you can update it? (It might be that gcc 7.2 simply does not build with such an old gcc, and then you'd have to get

Re: [sage-devel] Build fails: Sage 8.7 on Centos 6.10 x64

I set SAGE_INSTALL_GCC=no reran "make" on fresh un-tar and got... configure: No compiler with C++11 support was found configure: error: SAGE_INSTALL_GCC is set to 'no', but your C++ compiler does not support C++11 -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Build fails: Sage 8.7 on Centos 6.10 x64

oh easy - well... 1) the installed vendor gcc is 4.4.7 2) it does this by itself - I didnt ask it too - plain "make" is doing this. 3) I have: a) gcc-4.4.7-23.el6.x86_64 b) gcc-gfortran-4.4.7-23.el6.x86_64 c) gcc-c++-4.4.7-23.el6.x86_64 Those versions all match - as the doc says it

Re: [sage-devel] Re: bug: factoring symbolic expressions containing exponentials

On Wed, Apr 10, 2019 at 5:28 PM rjf wrote: > > > I suppose this is a Sage bug; Maxima doesn't have a problem with > its factor program. > Indeed. sage: ex=exp(2*x)+exp(-2*x); ex e^(2*x) + e^(-2*x) sage: maxima(ex).factor().sage() (e^(4*x) + 1)*e^(-2*x) sage: bool(maxima(ex).factor().sage()==ex)

Re: [sage-devel] Build fails: Sage 8.7 on Centos 6.10 x64

oh easy - well... 1) the installed vendor gcc is 4.4.7 2) it does this by itself - I didnt ask it too - plain "make" is doing this. 3) I have: a) gcc-4.4.7-23.el6.x86_64 b) gcc-gfortran-4.4.7-23.el6.x86_64 c) gcc-c++-4.4.7-23.el6.x86_64 Those versions all match - as the doc says it

[sage-devel] Re: bug: factoring symbolic expressions containing exponentials

I suppose this is a Sage bug; Maxima doesn't have a problem with its factor program. As you know, polynomial "factoring" is a process that mathematically is defined in a unique factorization domain, which is broken in the example at least 2 ways, by have a denominator, and by having

Re: [sage-devel] Build fails: Sage 8.7 on Centos 6.10 x64

Why are you building Sage's gcc? I can hardly imagine a situation you'd need it. See http://doc.sagemath.org/html/en/installation/source.html#linux-prerequisite-installation for details on this. On Wed, Apr 10, 2019 at 10:57 PM richr410 via sage-devel wrote: > > Hello, > > Ive tried a number of

[sage-devel] Build fails: Sage 8.7 on Centos 6.10 x64

Hello, Ive tried a number of tricks with "configure flags", LDFLAGS, etc - trying to get Sage to build. it "appears" the error 32 / 64 bit mismatching on the "ld" command. Source file used: sage-8.7.tar.gz To create log I posted here - I scrapped everything and did a completely fresh build

[sage-devel] bug: factoring symbolic expressions containing exponentials

sage: sage.version.version '8.6' sage: ex=exp(2*x)+exp(-2*x); ex e^(2*x) + e^(-2*x) sage: factor(ex) 2*e^(2*x) sage: bool(factor(ex)==ex) False sage: bool(factor(e^(2*x)+e^(-2*x))==e^(2*x)+e^(-2*x)) False sage: bool(factor(2^(2*x)+2^(-2*x))==2^(2*x)+2^(-2*x)) True -- You received this message

[sage-devel] Third update on Boolean-Cayley-graphs

An update on my previous post . So far my project to classify bent functions by their Cayley graphs has resulted in the following. - The paper "Classifying bent

Re: [sage-devel] ImportError: cannot import name SAGE_LOGS

On Wednesday, April 10, 2019 at 2:57:12 PM UTC+2, Jeroen Demeyer wrote: > > How did you notice that, i.e. why do you need SAGE_LOGS? > While releasing slabbe-0.5, I was making sure that all tests passed in all my modules, and I was using SAGE_LOGS here (a module just for fun anyways):

Re: [sage-devel] ImportError: cannot import name SAGE_LOGS

How did you notice that, i.e. why do you need SAGE_LOGS? I'm -1 on restoring SAGE_LOGS, since it's one of those things which confuses build-time and run-time. There should be no need to access the Sage build logs at run-time. On binary installations, there might not even be a logs directory.

[sage-devel] ImportError: cannot import name SAGE_LOGS

Bonjour, I just noticed the following change in sage.env: ┌┐ │ SageMath version 8.6, Release Date: 2019-01-15 │ │ Using Python 3.6.6. Type "help()" for help.│

Re: [sage-devel] libSingular not found

Yes, didn't realize that the command "sage" runs the executable installed. Thanks a lot, On Wednesday, April 10, 2019 at 6:02:06 PM UTC+5:30, E. Madison Bray wrote: > > On Wed, Apr 10, 2019 at 2:21 PM > wrote: > > > > I am trying to build a development branch of sage related to this ticket >

Re: [sage-devel] libSingular not found

On Wed, Apr 10, 2019 at 2:21 PM wrote: > > I am trying to build a development branch of sage related to this ticket > (27482) If you are working with Sage in a source code checkout, run `./sage`. Running `sage` means you'll run the sage executable installed on your system path, which is

Re: [sage-devel] libSingular not found

I am trying to build a development branch of sage related to this ticket (27482) On Wednesday, April 10, 2019 at 5:45:55 PM UTC+5:30, E. Madison Bray wrote: > > On Wed, Apr 10, 2019 at 1:25 PM > wrote: > > > > I want to build the documentation of my

Re: [sage-devel] libSingular not found

On Wed, Apr 10, 2019 at 1:25 PM wrote: > > I want to build the documentation of my branch, but running sage --docbuild > html gives following error:- > Traceback (most recent call last): > File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main > mod_name, _Error) > File

[sage-devel] libSingular not found

I want to build the documentation of my branch, but running sage --docbuild html gives following error:- Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main mod_name, _Error) File "/usr/lib/python2.7/runpy.py", line 111, in