[sage-devel] Re: [sage-trac-account] Corrections about the function "is_prime" for graphs

in fact, the output quite telling: sage: g1=Graph({0:[1,4],1:[0,2,4],2:[1,3,4],3:[2],4:[0,1,2]});g2=Graph({0:[1],1:[0,2,4],2:[1,3,4],3:[2,4],4:[1,2,3]}) sage: g1.is_prime() /home/dima/Sage/sage-dev/local/lib/python2.7/site-packages/sage/graphs/graph.py:6842:

[sage-devel] Re: [sage-trac-account] Corrections about the function "is_prime" for graphs

Sooner or later it was bound to happen; this function relies on modular_decomposition optional package, which is very iffy, and ought to be removed or redone, see https://trac.sagemath.org/ticket/17950 Should we do something about it? @Harald - you can see the sender email by doing show

[sage-devel] Fwd: [sage-trac-account] Corrections about the function "is_prime" for graphs

This came in via the trac account request. I don't know the sender's email address ... -- h -- Forwarded message -- From: 'Jamel Dammak' via sage-trac-account Date: Sun, Dec 11, 2016 at 10:01 PM Subject: [sage-trac-account] Corrections about

Re: [sage-devel] Updates or hints on "latex Function Prevent Simplification"?

Dear Qian, all, I was privately asked to send over some information on extracting a formula dataset out of arXiv.org, which we have had some experience with in prof. Michael Kohlhase's KWARC research group. I gave a talk earlier in the year [1] where I reported we have so far managed to

[sage-devel] Re: Python3-compatible syntax

> Regression in the move to python3 is happening all the time, and it is > indeed very annoying. > > Making a test target and a buildbot may be easier once at least all our > cython files are correctly cythonized in py3. This is blocked by the > removal of cmp() in all .pyx files. Not an easy

[sage-devel] Re: Sage for Windows installer (take 2)

For the hell of it, I tried this installer on a "spare" Windows VM. Bravo, bravissimo ! Now, there might be some use to all those Windows boxes... I tried to install some optional package ; it turns out that the installed setup isindeed minimal : (sage-sh) charpent@DESKTOP-P0B7HOE:~$ time (

[sage-devel] Re: Python3-compatible syntax

Hello, Regression in the move to python3 is happening all the time, and it is indeed very annoying. Making a test target and a buildbot may be easier once at least all our cython files are correctly cythonized in py3. This is blocked by the removal of cmp() in all .pyx files. Not an easy

[sage-devel] Re: Python3-compatible syntax

Sun 2016-12-11 09:14:01 UTC+1, Jori Mäntysalo: > Latest beta is now almost Python3-compatible at syntax level, that is > > find src/sage -name '*.py' | xargs -n 1 python3 -m py_compile > > outputs almost nothing. However, there is now a lambda-line in > src/sage/graphs/generators/smallgraphs.py

[sage-devel] Python3-compatible syntax

Latest beta is now almost Python3-compatible at syntax level, that is find src/sage -name '*.py' | xargs -n 1 python3 -m py_compile outputs almost nothing. However, there is now a lambda-line in src/sage/graphs/generators/smallgraphs.py that needs Python2. Please check you syntax against Py3