[sage-devel] Re: Issue with quick start

On Friday, December 1, 2017 at 6:43:05 AM UTC-8, kcrisman wrote: > > > > On Thursday, November 30, 2017 at 6:50:09 PM UTC-5, Matthew Schroeder > wrote: >> >> Dear John, >> >> Thank you for your interest in resolving this problem. >> >> To answer your question I am referring to >>

[sage-devel] Re: Issue with quick start

On Thursday, November 30, 2017 at 12:22:05 PM UTC-8, Matthew Schroeder wrote: > > i did some research. Please see the link: Saying "Maths" is wrong > > Turns out this is a problem that should be fixed. > I assume you're joking. With this

[sage-release] Re: Sage 8.1.rc0 released

On Friday, November 17, 2017 at 10:40:22 AM UTC-8, Simon King wrote: > > Hi John, > > On 2017-11-17, John H Palmieri <jhpalm...@gmail.com > wrote: > >> And WHY that change was made! > >> > > > > If it takes a while to build the documentat

[sage-release] Re: Sage 8.1.rc0 released

On Friday, November 17, 2017 at 6:37:54 AM UTC-8, Simon King wrote: > > On 2017-11-17, Kwankyu Lee wrote: > > Ah, I didn't know that. This (building the documentation is no longer > the > > last step) sounds a big change to me. I wonder when that change was > made. > >

Re: [sage-release] Re: Sage 8.1.rc0 released

are testing. Can anyone else reproduce this? On Thursday, November 9, 2017 at 2:44:43 PM UTC-8, François Bissey wrote: > > Smells like https://trac.sagemath.org/ticket/23742 > > > On 10/11/2017, at 11:31, John H Palmieri <jhpalm...@gmail.com > > wrote: > >

[sage-release] Re: Sage 8.1.rc0 released

WIth OS X 10.12.6, Xcode (and the same happens when building with clang, #12426): sage -t --long --warn-long 64.0 src/sage/matrix/matrix_mod2_dense.pyx # Killed due to kill signal ** Tests run before process (pid=12556)

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

) in favor of another option : 10 > >> people > > > > > > No : make that 7 people... > > > >> > >> David Joyner > >> Michael Orlitzky > >> Nicolas M Thiéry > >> Dr David Kirby > >> Thierry (sag

[sage-support] Re: which browser

Have you tried setting the BROWSER environment variable? If that doesn't work, what about SAGE_BROWSER? John On Friday, October 20, 2017 at 7:38:58 AM UTC-7, John Cremona wrote: > > On 20 October 2017 at 15:34, John Cremona > wrote: > > I am running Sage on a linux

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

On Thursday, October 19, 2017 at 2:17:10 PM UTC-7, Dima Pasechnik wrote: > > the 1-click openssl install image for OSX is called Xcode, and one can go > for a long lunch while waiting for it to finish, even on a fast network... > > Apple should pick up the bill for these lunches, and much more,

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

his point, I don't even understand what the error is... Any > suggestions? > > > On Monday, October 16, 2017 at 5:11:15 PM UTC-4, John H Palmieri wrote: >> >> You have at least two choices. For both, start by downloading ( >> http://www.sagemath.org/download-source.ht

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

You have at least two choices. For both, start by downloading (http://www.sagemath.org/download-source.html) and unpacking sage-8.0.tar.gz wherever you plan to build it. Choice 1: install git-trac-config: see

[sage-devel] Re: python3 status

That's great! Thank you for all of your work on this. John On Friday, October 13, 2017 at 8:56:11 AM UTC-7, Frédéric Chapoton wrote: > > Hello, > > I have reached this point with the ugly python3 experimental branch > "public/python3-experiment-8.1.b7": > > >

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Also, if you have problems with the curl package, try https://trac.sagemath.org/ticket/23991 On Sunday, October 8, 2017 at 10:02:36 AM UTC-7, John H Palmieri wrote: > > Are you trying to install Sage 6.2 (as your log seems to indicate)? That > is extremely old. Try with a fre

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

Are you trying to install Sage 6.2 (as your log seems to indicate)? That is extremely old. Try with a fresh source installation: either http://www.sagemath.org/download-source.html for stable source or http://www.sagemath.org/download-latest.html for the latest development version. Also, do

[sage-devel] Request reviewers for trac 23898, update our version of GCC

At https://trac.sagemath.org/ticket/23898, I propose updating to GCC 7.2.0. This seems to fix the problem with building Sage with Apple's latest version of Xcode (there is also separate work going to let Sage build with clang with the latest Xcode: #12426 and #23922). I have tested this on a

[sage-devel] Re: sage / gcc build failed on macOS High Sierra

The problem with gcc has been reported here: https://trac.sagemath.org/ticket/23898. No one seems to have made any progress on it. In the meantime, I've been able to build Sage using https://trac.sagemath.org/ticket/12426 and https://trac.sagemath.org/ticket/23922. (In my case this is with

[sage-devel] Re: doctesting tab completion

Is there a typo? Should the line causing the crash start with "from"? (Same question on the trac ticket.) On Wednesday, September 27, 2017 at 8:55:16 PM UTC-7, Dima Pasechnik wrote: > > How does one write a doctest for tab completion on the command line? > I don't care for the output, I just

Re: [sage-devel] let's make FriCAS optional

On Wednesday, September 27, 2017 at 10:40:36 AM UTC-7, Jeroen Demeyer wrote: > > On 2017-09-27 16:10, Vincent Delecroix wrote: > > Not sufficient: the package has to be useful for Sage and used in > > Sage... emacs is unlikely to become an optional package even if it > > satisfies the above

Re: [sage-devel] Is trac down?

On Tuesday, September 26, 2017 at 1:56:39 PM UTC-7, mforets wrote: > > > > El martes, 26 de septiembre de 2017, 22:38:23 (UTC+2), Samuel Lelievre > escribió: >> >> Tue2017-09-26 10:29:17 UTC, Maarten Derickx: >> > Seems to be back up again. >> >> Not sure if it's related but when I click on the

Re: [sage-devel] Consider not upgrading to Xcode 9.0

Trying to build gfortran yields the same error as reported at https://trac.sagemath.org/ticket/23898. John On Wednesday, September 20, 2017 at 3:08:05 PM UTC-7, John H Palmieri wrote: > > I successfully built with the current version (not the updated one) of > eclib plus the

Re: [sage-devel] Consider not upgrading to Xcode 9.0

problem that was spotted > > before. It proved effective in this instance. So I will proceed with > trying > > to build the rest of sage. > > > > François > > > >> On 21/09/2017, at 04:05, John H Palmieri <jhpalm...@gmail.com > > wrote: >

[sage-devel] Re: Consider not upgrading to Xcode 9.0

a big problem, some rather standard C++ > template issue to be tweaked... > > On Wednesday, September 20, 2017 at 12:50:32 AM UTC+1, John H Palmieri > wrote: >> >> I just upgraded an OS X box to Xcode 9.0, and now Sage doesn't build: >> >> - with a fresh

[sage-devel] Consider not upgrading to Xcode 9.0

I just upgraded an OS X box to Xcode 9.0, and now Sage doesn't build: - with a fresh Sage 8.1.beta5 tarball, gcc doesn't build: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2: error: no member named 'fancy_abort' in namespace

[sage-devel] Signs and graded algebras

I have a graded algebra A over a field k, and I would like the following behavior: when I multiply homogeneous elements of the tensor square (A tensor A), I want signs to appear, as in: (a tensor b) (c tensor d) = (-1)^(deg b deg c) (ac tensor bd) You could ask for the same when multiplying

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

By the way, if the problem can be reduced to building the documentation (that is, if "make build" succeeds but "make" does not), another option would be to try "make doc-html-no-plot", or essentially equivalently do export SAGE_DOCBUILD_OPTS+=' --no-plot' make It is possible that the

[sage-support] Re: Problem with upgrade on OS X

Sage will build its own gcc, so as long as you have some functioning version of gcc, you shouldn't need to worry about upgrading that. Just try installing a new version of Sage (from scratch, not by upgrading 6.7) and see what happens. John On Thursday, September 7, 2017 at 8:56:03 AM

Re: [sage-devel] Does anyone use SAGE64?

On Saturday, September 2, 2017 at 11:54:00 AM UTC-7, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: > > On 2 September 2017 at 01:41, John H Palmieri <jhpalm...@gmail.com > > wrote: > >> >> >> Hi Dave, >> >> Can you clarify? You say that the

Re: [sage-devel] Does anyone use SAGE64?

On Friday, September 1, 2017 at 3:47:28 PM UTC-7, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: > > > On 1 Sep 2017 23:21, "John H Palmieri" <jhpalm...@gmail.com > > wrote: > > > > Does anyone use the environment variables SAGE64 of CFLAG64? At

[sage-devel] Does anyone use SAGE64?

Does anyone use the environment variables SAGE64 of CFLAG64? At https://trac.sagemath.org/ticket/23733, it is suggested that they be deprecated and then removed. Any comments? -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: python3 in sage

On Thursday, August 24, 2017 at 2:50:09 PM UTC-7, William wrote: > > On Thu, Aug 24, 2017 at 2:17 PM, Nils Bruin > wrote: > > On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote: > >> > >> I'm not sure what the status is these days, but we may want to stop > >>

[sage-devel] Re: Error Compiling Sage 8.0 from Source

Or as a stopgap, try building with the command OPENBLAS_CONFIGURE="TARGET=HASWELL" make On Thursday, August 17, 2017 at 2:00:03 PM UTC-7, Dima Pasechnik wrote: > > OK, this is what they call Kaby Lake H. > > You may try the patch on > https://trac.sagemath.org/ticket/23272 > (it also upgrades

Re: [sage-support] Re: Sage Crash Report

On Tuesday, August 15, 2017 at 9:49:35 PM UTC-7, William wrote: > > On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri <jhpalm...@gmail.com > > wrote: > >> One of the very last lines of the report says >> >>> >>> ImportError: libgfortran.so

[sage-support] Re: Sage Crash Report

One of the very last lines of the report says > > ImportError: libgfortran.so.3: cannot open shared object file: No such file > or directory > > You need to install gfortran on your computer. On Tuesday, August 15, 2017 at 6:15:01 PM UTC-7, kats...@gmail.com wrote: > > Sage Crash Report > --

[sage-support] Re: Calling java classes from Sage using Py4J

In Sage, "10" is a Sage integer, not a Python int. I am guessing that gateway.jvm.java.util.Random.nextInt expects a Python int for its input, and when it gets a Sage Integer, that causes a problem. What happens if you replace "random.nextInt(10)" with "random.nextInt(int(10))"? On

[sage-support] Re: numerical semigroup in sagemath

On Tuesday, July 25, 2017 at 5:53:37 AM UTC-7, springfield .gion wrote: > > Hi, I need to create and manipulate the additive semigroups generated by > integers (such as those generated by tuples of coprime integers), but I am > struggling with the syntax; is there an easy way to create

[sage-support] Re: sage installation on kubuntu 16.04

One of the last lines in the crash report: ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory It looks like you need to install gfortran. -- John On Sunday, July 23, 2017 at 2:54:43 AM UTC-7, Santosh Pattanayak wrote: > > Hello, > I tried

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

I just had the same problem with a new computer (Kaby Lake processor, apparently). Can we patch OpenBLAS to fall back to ATOM if it's x86_64 but can't detect the precise CPU? (I can't do this, but maybe someone else can.) John On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik

[sage-support] Re: Sage Crash Report

On Sunday, June 18, 2017 at 4:41:22 AM UTC-7, Dima Pasechnik wrote: > > git repo is not relevant, but a python module that shadows a Sage python > module would be a problem. For example, if you have your own file "parser.py", it would interfere with the standard Python module "parser". --

Re: [sage-devel] Option for docbuilding without plots?

Also "make doc-html-no-plot" as documented here: http://doc.sagemath.org/html/en/installation/source.html#make-targets John On Saturday, June 17, 2017 at 12:26:21 AM UTC-7, Thierry (sage-googlesucks@xxx) wrote: > > Hi, > > each of the following should work: > > export

Re: [sage-support] Re: typo in simplicial complex documentation?

On Sunday, June 11, 2017 at 10:13:52 AM UTC-7, David Joyner wrote: > > On Sun, Jun 11, 2017 at 11:30 AM, John H Palmieri > <jhpalm...@gmail.com > wrote: > > > > > > On Saturday, June 10, 2017 at 7:05:49 PM UTC-7, David Joyner wrote: > >> > >&g

Re: [sage-support] Re: typo in simplicial complex documentation?

On Saturday, June 10, 2017 at 7:05:49 PM UTC-7, David Joyner wrote: > > On Thu, Jun 8, 2017 at 10:49 PM, John H Palmieri <jhpalm...@gmail.com > > wrote: > > > > > > On Thursday, June 8, 2017 at 5:16:15 PM UTC-7, David Joyner wrote: > >> > &g

[sage-support] Re: typo in simplicial complex documentation?

On Thursday, June 8, 2017 at 5:16:15 PM UTC-7, David Joyner wrote: > > Hi all: > > This is kind of a newbie question, as I'm not an expert on simplicial > complexes. It's also a minor technical issue on the documentation, not > the code. > > I'm trying to debug some code of mine and, on

[sage-support] Re: Sage Crash Report

"ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory" It looks like you need to install fortran on your machine. On Monday, June 5, 2017 at 10:12:12 AM UTC-7, Vincent HERBERT wrote: > > > -- You received this message because you are subscribed to the

[sage-devel] Sage Python 3 proposal

I have a proposal for making the transition to use Sage with Python 3. See https://trac.sagemath.org/ticket/23119 for details (and a branch which works, at least in my limited testing). The proposal: - Have a new command "sage3" which runs Sage using Python 3. - If you build Sage with the

[sage-release] Re: Sage 8.0.beta8 released

I'm getting intermittent timeouts from src/sage/doctest/external.py, and in particular the "has_mathematica()" test. This is a new (but underpowered) computer and it does not have mathematica installed. If I run $ sage --sh $ math-readline then 19 out of 20 times, it fails immediately,

[sage-devel] Re: python3 : help needed

On Friday, May 26, 2017 at 8:40:22 AM UTC-7, Nils Bruin wrote: > > On Friday, May 26, 2017 at 7:52:57 AM UTC-7, John H Palmieri wrote: >> >> If you build Sage's IPython package with SAGE_PYTHON3=yes, then it will >> install a script local/bin/ipython3. (Note then t

[sage-devel] Re: python3 : help needed

On Thursday, May 25, 2017 at 6:11:02 PM UTC-7, Nils Bruin wrote: > > On Thursday, May 25, 2017 at 5:07:22 PM UTC-7, John H Palmieri wrote: >> >> >> >> On Thursday, May 25, 2017 at 4:40:01 PM UTC-7, Nils Bruin wrote: >>> >>> incidentally, it w

[sage-devel] Re: python3 : help needed

On Thursday, May 25, 2017 at 4:40:01 PM UTC-7, Nils Bruin wrote: > > incidentally, it would be nice if we could equiv local/bin/ipython with > the proper sage-python23 as well. Having a functional shell with an > interactive debugger is a much nicer way to debug "import sage.all". > This is a

[sage-devel] Re: python3 : help needed

On Thursday, May 25, 2017 at 10:08:21 AM UTC-7, Kwankyu Lee wrote: > > The successful launch with my built of sage with python3 seems well > explained by John. > > On Thursday, May 25, 2017 at 5:37:10 PM UTC+2, Frédéric Chapoton wrote >> >> The road towards a full python3 sage is still quite

[sage-devel] Re: python3 : help needed

On Thursday, May 25, 2017 at 1:49:34 AM UTC-7, Frédéric Chapoton wrote: > > ok, now with 8.0.b8, you can just do > > "export SAGE_PYTHON3=yes" > > and then "make build". This should succeed, with no error message. > > Then try "./sage" > > This fails with some traceback about not finding

[sage-devel] Re: python3 : help needed

On Thursday, May 25, 2017 at 7:49:42 AM UTC-7, Kwankyu Lee wrote: > > > > On Thursday, May 25, 2017 at 4:36:04 PM UTC+2, Frédéric Chapoton wrote: >> >> Very surprising that sage starts.. Did you really launch the sage that >> you just compiled ? >> > > I suspect this as well... I will respond

[sage-release] Re: Sage 8.0.beta7 released

I have two problems with the Jupyter notebook in Sage 8.0.beta7 on OS X. First, starting up: if I give the command "sage -n" (or "sage -n jupyter"), I see Copy/paste this URL into your browser when you connect for the first time, to login with a token:

[sage-devel] Re: python3 : help needed

On Saturday, May 20, 2017 at 1:12:48 PM UTC-7, John H Palmieri wrote: > > In the file src/sage_setup/clean.py, the variable CEXTMOD_EXTS could > perhaps be modified from (on OS X) ".so" to ".cpython-36m-darwin.so". That > fixes the problem for me, but I'm not

[sage-devel] Re: python3 : help needed

On Saturday, May 20, 2017 at 8:33:20 AM UTC-7, John H Palmieri wrote: > > We do not have a plan for how to *run* Sage using Python3, only for how to > build it: set SAGE_PYTHON3=yes. Should there be a separate command, > `sage3`, which uses Python3? Or once you build with SAGE

[sage-devel] Re: python3 : help needed

On Saturday, May 20, 2017 at 1:12:48 PM UTC-7, John H Palmieri wrote: > > In the file src/sage_setup/clean.py, the variable CEXTMOD_EXTS could > perhaps be modified from (on OS X) ".so" to ".cpython-36m-darwin.so". That > fixes the problem for me, but I'm not

[sage-devel] Re: python3 : help needed

; Yes, this unicode error will be the next one we need to handle. But first >> we need to understand what is going wrong before. Commenting the line in >> src/setup.py is certainly not the right solution.. >> >> >> Le samedi 20 mai 2017 00:43:25 UTC+2, John H Palmieri

[sage-devel] Re: python3 : help needed

t is going wrong before. Commenting the line in > src/setup.py is certainly not the right solution.. > > > Le samedi 20 mai 2017 00:43:25 UTC+2, John H Palmieri a écrit : >> >> >> >> On Friday, May 19, 2017 at 3:27:54 PM UTC-7, John H Palmieri wrote: >>>

[sage-devel] Re: python3 : help needed

wrong before. Commenting the line in >> src/setup.py is certainly not the right solution.. >> >> >> Le samedi 20 mai 2017 00:43:25 UTC+2, John H Palmieri a écrit : >>> >>> >>> >>> On Friday, May 19, 2017 at 3:27:54 PM UTC-7, John H Palmieri w

[sage-devel] Re: python3 : help needed

On Friday, May 19, 2017 at 3:27:54 PM UTC-7, John H Palmieri wrote: > > > > On Friday, May 19, 2017 at 2:46:15 PM UTC-7, John H Palmieri wrote: >> >> >> >> On Friday, May 19, 2017 at 9:51:46 AM UTC-7, Frédéric Chapoton wrote: >>> >>> Dear al

[sage-devel] Re: python3 : help needed

On Friday, May 19, 2017 at 2:46:15 PM UTC-7, John H Palmieri wrote: > > > > On Friday, May 19, 2017 at 9:51:46 AM UTC-7, Frédéric Chapoton wrote: >> >> Dear all, >> >> We have almost reached the state of vanilla sage building with >> SA

[sage-devel] Re: python3 : help needed

On Friday, May 19, 2017 at 9:51:46 AM UTC-7, Frédéric Chapoton wrote: > > Dear all, > > We have almost reached the state of vanilla sage building with > SAGE_PYTHON3=yes (this does not mean working !). But something seems to go > wrong, and I would like help to find and fix the current

[sage-devel] Docstring standards: new Sphinx directives? New Sphinx directions?

Regarding the current polling for docstring guidelines and standards, perhaps it would be better to write docstrings in a form like def f(...): """ one line description, as we currently have .. INPUT:: input block, maybe an itemized list .. OUTPUT:: output

[sage-devel] Re: Second round poll for H1 a specific guideline for writing docstrings

+1 -- 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.com. To post to this group, send email to sage-devel@googlegroups.com.

Re: [sage-devel] Poll for issue G5 a specific guideline for writing docstrings

+1 to OUTPUT: lattice when possible. On Wednesday, May 17, 2017 at 8:05:21 AM UTC-7, Jeroen Demeyer wrote: > > What about > > OUTPUT: lattice > > Unlike an INPUT, an OUTPUT is not a list of things. So why format it as > a list? A list could be useful for example in > > OUTPUT: a tuple

[sage-devel] Re: Poll for issue G1 a specific guideline for writing docstrings

On Wednesday, May 17, 2017 at 7:07:29 AM UTC-7, Kwankyu Lee wrote: > > We do a poll for adopting an official guideline for docstrings (see > https://trac.sagemath.org/ticket/23017) > > G1. Write > > Return True if something is true. > > but do not write > > Return ``True`` if

[sage-support] Re: persistent homology?

Sage has no interface to any persistent homology software. Please write one! -- John On Friday, May 12, 2017 at 4:20:14 AM UTC-7, Dima Pasechnik wrote: > > > > On Friday, May 12, 2017 at 9:49:20 AM UTC+1, Pierre wrote: >> >> Is there any interface between Sage and persistent homology software?

Re: [sage-devel] Sage policy question: require docstrings and doctests?

On Wednesday, May 10, 2017 at 2:25:33 AM UTC-7, Erik Bray wrote: > > On Tue, May 9, 2017 at 9:14 PM, John H Palmieri <jhpalm...@gmail.com > > wrote: > > Sage's developer's guide says: "Every function must have a docstring" > which > > must

[sage-devel] Sage policy question: require docstrings and doctests?

Sage's developer's guide says: "Every function must have a docstring" which must include "An EXAMPLES block for examples. This is not optional." What is meant by "function"? Here is an example, taken from ticket #21399: import sys if sys.platform == X: def auxiliary_function(...):

[sage-support] Re: Use of \Bold in latex methods, and SageTeX

Hi John, Within Sage, you can get the appropriate command with sage: from sage.misc.latex_macros import sage_configurable_latex_macros sage: sage_configurable_latex_macros ['\\newcommand{\\Bold}[1]{\\mathbf{#1}}'] sage: print(sage_configurable_latex_macros[0]) \newcommand{\Bold}[1]{\mathbf{#1}}

Re: [sage-devel] pip install on MacOS

This is not a solution to the pip/ssl problem, but for a single package like snakeviz, you can go to https://pypi.python.org/pypi/snakeviz, download the tar.gz file, and then do sage -pip install /path/to/snakeviz-0.4.1.tar.gz -- John On Friday, May 5, 2017 at 9:11:48 AM UTC-7, Nicolas

[sage-support] Re: vars() gives me an error message

See #22941 for a separate approach (independent of #22933, each ticket fixes a different problem). John On Tuesday, May 2, 2017 at 2:33:27 PM UTC-7, Dima Pasechnik wrote: > > this is now #22933, ready for review. > > Note that it's not a complete fix; > > sage: vars() > > still fails > >

[sage-devel] Re: vars() gives me an error message

See #22941 for a separate approach (independent of #22933, each ticket fixes a different problem). John On Tuesday, May 2, 2017 at 2:33:27 PM UTC-7, Dima Pasechnik wrote: > > this is now #22933, ready for review. > > Note that it's not a complete fix; > > sage: vars() > > still fails > >

[sage-devel] Re: vars() gives me an error message

I think it's a (pretty?) printing problem. For me, running sage: a = vars() works without error, but then sage: a gives the error. Same thing happens with locals(). -- John On Tuesday, May 2, 2017 at 2:37:25 AM UTC-7, Dima Pasechnik wrote: > > Indeed, it appears that vars() is

Re: [sage-devel] building pdf docs fails

On Saturday, April 29, 2017 at 8:34:50 AM UTC-7, John H Palmieri wrote: > > > > On Saturday, April 29, 2017 at 8:33:20 AM UTC-7, John H Palmieri wrote: >> >> 'iftex' is required directly because of line 311 in >> src/doc/common/conf.py: >> >> \usepa

Re: [sage-devel] building pdf docs fails

On Saturday, April 29, 2017 at 8:33:20 AM UTC-7, John H Palmieri wrote: > > 'iftex' is required directly because of line 311 in src/doc/common/conf.py: > > \usepackage{iftex} > > This was added in https://trac.sagemath.org/ticket/22252, to compensate > for the fact

Re: [sage-devel] building pdf docs fails

'iftex' is required directly because of line 311 in src/doc/common/conf.py: \usepackage{iftex} This was added in https://trac.sagemath.org/ticket/22252, to compensate for the fact that Sphinx no longer included it by default. The 'iftex' package is part of TeXLive; I don't know about other TeX

[sage-devel] Re: Simplicial complexes' .faces(subcomplex) breaks self?

This can be fixed by changing (on line 2554) "L.faces()[dim]" to "L.n_cells(dim)". See https://trac.sagemath.org/ticket/22880 -- John On Wednesday, April 26, 2017 at 12:17:13 PM UTC-7, Mikhail Tyomkin wrote: > > Hi everyone. > > The following code raises a KeyError on the last line (say, in

Re: [sage-devel] Re: Trac slow

On Thursday, April 20, 2017 at 9:25:12 AM UTC-7, Daniel Krenn wrote: > > On 2017-04-20 17:09, John H Palmieri wrote: > > Since some time last night, I have been unable to use "git trac checkout > > TICKET": > > This (other ticket) worked for me about an hou

Re: [sage-devel] Re: Trac slow

Since some time last night, I have been unable to use "git trac checkout TICKET": $ git trac checkout 22764 Loading ticket #22764... Checking out Trac #22764 remote branch fb90d5e3667237f2d9fc7ba982b466bc52802b1d -> local branch t/22764/fb90d5e3667237f2d9fc7ba982b466bc52802b1d... Traceback

Re: [sage-devel] OSX Xcode 8.3 breaks openblas

Right, I have haswell. John On Monday, April 10, 2017 at 3:22:49 PM UTC-7, Volker Braun wrote: > > It might be hardware specific; I take it you don't have a sandy bridge CPU? > > > > On Tuesday, April 11, 2017 at 12:19:26 AM UTC+2, John H Palmieri wrote: >> >

Re: [sage-devel] OSX Xcode 8.3 breaks openblas

I ran Xcode to make sure it would update any component pieces and then ran a build from scratch. Openblas built just fine for me (same Xcode version). John On Monday, April 10, 2017 at 3:00:19 PM UTC-7, François wrote: > > I may need to try a build from scratch, takes time (to build gcc

Re: [sage-release] Re: Sage 8.0.beta1 released

On Sunday, April 9, 2017 at 12:03:03 AM UTC-7, Jeroen Demeyer wrote: > > On 2017-04-08 14:23, Eric Gourgoulhon wrote: > > make ptestlong created > > an empty directory "home" in SAGE_ROOT > > That's an old issue. I never investigated where that "home" came from. > I finally tracked that

[sage-devel] Re: sage-8.0 beta and python3

Python 3 is also built and installed by default in Sage, at least in recent development versions, for use by developers trying to make Sage compatible with Python 3. -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-release] Re: Sage 8.0.beta1 released

With a clean tarball, "./sage -i PKG" fails: Error: You must set either the SAGE_LOCAL or SAGE_SCRIPTS_DIR environment variable to run this Error setting environment variables by sourcing '/Users/palmieri/Desktop/TEMP/sage-8.0.beta1/src/bin/sage-env'; possibly contact sage-devel (see

[sage-devel] Proposal: remove SAGE_LOCAL/lib/python

Did that subject line get your attention? I propose that we remove the symbolic link SAGE_LOCAL/lib/python, keeping the two directories SAGE_LOCAL/lib/python2.7 and SAGE_LOCAL/lib/python3.5. The link points to python2.7 by default. I can't tell if this is a major proposal or a minor one, so I

[sage-release] Re: About matplotlib 2

Matplotlib version is 1.5.1. You can look in SAGE_ROOT/local/var/lib/sage/installed to see a file for each Sage package, including a version number. Also, as Justin points out, you can look at SAGE_ROOT/build/pkgs, and in particular SAGE_ROOT/build/pkgs/matplotlib/package-version.txt. Python

Re: [sage-support] Re: OS X 10.12

binary package. Or recompile Sage from scratch in the new location > ("make distclean && make") > > snapdragon:~ joshua$ > > > > > > On Mar 31, 2017, at 5:49 PM, John H Palmieri <jhpalm...@gmail.com > > wrote: > > Thi

[sage-support] Re: OS X 10.12

Is is also possible that a homebrew installation is interfering? I have seen claims that it can interfere with building Sage from scratch, but I don't see why it would cause problems with installing from a pre-built binary. John On Friday, March 31, 2017 at 4:09:05 PM UTC-7, Volker Braun

[sage-support] Re: OS X 10.12

This looks strange. It ought to look like this the first time you run Sage, and this is what happens when I download and install from that file: Rewriting paths for your new installation directory === This might take a few minutes but only has to

[sage-devel] Re: making a reset() makes it impossible to "quit"

It looks like a bug to me. ┌┐ │ SageMath version 7.6, Release Date: 2017-03-25 │ │ Type "notebook()" for the browser-based notebook interface.│ Type "help()" for help.

[sage-devel] 'make PACKAGE' does not build the toolchain

If I unpack a Sage tarball, what should happen when I run 'make lcalc', for example? Should it be the same as running 'make', but stopping after the lcalc build? Right now, that does not seem to be the case: 'make lcalc' does not build the toolchain target, so on OS X or other systems requiring

[sage-release] Re: Sage 7.6.rc0 released

On OS X with TeXLive 2016, the PDF documentation fails to build for me, the Russian tutorial in particular: [docpdf] Underfull \hbox (badness 1) in paragraph at lines 300--300 [docpdf] [docpdf] (/usr/local/texlive/2016/texmf-dist/tex/latex/cyrillic/t2acmss.fd)<>< [docpdf] ><><> [docpdf]

[sage-support] Re: Multivariate polynomial coefficients including zeros

As I posted at http://stackoverflow.com/questions/42812634/multivariate-polynomial-coefficients-including-zeros, you could use lcm(f.monomials()) to get the least common multiple of the monomials in f, and then plug that into P.monomial_all_divisors(lcm(...)) to get all monomials which

Re: [sage-devel] tachyon-0.98.9.p5 build error in Linux

Although it's not a good idea to build Sage as root. I think it is likely to fail -- someone please correct me if I'm wrong. John On Tuesday, March 7, 2017 at 6:37:33 PM UTC-8, François wrote: > > Not at all. It has to do with sage’s python including this patch > >

[sage-support] Re: Sage Crash Report. appears to have loaded, failed to run.

Just about the last line in your crash report says ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory So you need to install gfortran, however that is done with Fedora. An internet search suggests something like "yum install gcc-gfortran". -- John

[sage-devel] Sage creates some *.pyc files in src/sage

If I run "make" in Sage, it creates some *.pyc files in src/sage: $ find src/sage -name "*.pyc" -print ./__init__.pyc ./env.pyc ./misc/__init__.pyc ./misc/lazy_import_cache.pyc ./misc/package.pyc ./repl/__init__.pyc ./repl/ipython_kernel/__init__.pyc ./repl/ipython_kernel/install.pyc

[sage-devel] Re: integration algorithms

Calculus classes today do not typically teach the Risch algorithm, in my experience. However, you shouldn't design calculus courses at most places based on experiences with MIT students. I think it is an interesting question about how much time we should spend teaching *how* to compute

Re: [sage-devel] Names of special methods like _pari_

On Tuesday, February 28, 2017 at 1:16:53 PM UTC-8, Jeroen Demeyer wrote: > > On 2017-02-28 20:46, Johan S. H. Rosenkilde wrote: > > In that case, it > > could be seen as an implementation detail that objects have the _pari > > method, and private would be apt. > > Yes, it's an

Re: [sage-support] Re: [sage 7.4] Error building OpenBlas

On Thursday, February 2, 2017 at 1:53:43 PM UTC-8, João Alberto Ferreira wrote: > > Well, I read somewhere about this procedure of moving the directory before > starting sage, but the Installation Manual seems to tell the same thing. > > "The directory where you built Sage is *NOT* hardcoded.

Re: [sage-devel] Re: Our SSL serial drama-cum-cliffhanger

The question is, if you have homebrew installed, can you build Sage from source? That is, extract the source tarball, type 'make' in the sage directory, and have it complete successfully. I think the motivation behind the question is, in the past, the presence of fink or macports prevented

<    3   4   5   6   7   8   9   10   11   12   >