Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

Last question was silly: it built just fine for me at the end of last year, with the same version number of the OS. Still, why would 10.14 be appearing in the log? On Tuesday, June 8, 2021 at 11:51:02 AM UTC-7 Paul Masson wrote: > It does not. This time it ran through the documentation bu

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

> How about > > make ptest > > ? > > Does this get you past building, and onto > testing ? > > > > On Tue, 8 Jun 2021, 06:39 Paul Masson, wrote: > >> And that didn't work either. Build hangs at the end of documentation: >> >>

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

And that didn't work either. Build hangs at the end of documentation: [dochtml] Elapsed time: 1773.8 seconds. [dochtml] Done building the documentation! Then nothing more. On Monday, June 7, 2021 at 7:35:09 PM UTC-7 Paul Masson wrote: > The documentation builds but the remainder d

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

The documentation builds but the remainder does not. If I then run "make build" it still hangs at the same line. Will try "make distclean" followed by single "make". It appears to be building the documentation too early. On Monday, June 7, 2021 at 7:08

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

TC-7 David Roe wrote: > Can you outline the steps you're taking from the beginning? I think Dima > is suggesting that the only reason that you'd see [sage_docbuild-9.4.beta0] > is if you used `make` rather than `make build`. > David > > On Mon, Jun 7, 2021 at 7:10 PM Paul Masson

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

> is suggesting that the only reason that you'd see [sage_docbuild-9.4.beta0] > is if you used `make` rather than `make build`. > David > > On Mon, Jun 7, 2021 at 7:10 PM Paul Masson wrote: > >> That's precisely what I'm doing! >> >> On Monday, June 7, 2021 at 4:0

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

That's precisely what I'm doing! On Monday, June 7, 2021 at 4:08:20 PM UTC-7 dim...@gmail.com wrote: > you don't need to build docs per se, just do > > make build > > > > On Tue, 8 Jun 2021, 00:05 Paul Masson, wrote: > >> Let me preface this issue by saying that I

[sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

Let me preface this issue by saying that I don't use Sage much because I prefer to work in pure JavaScript. I'm only trying to build in order to upgrade Three.js. The process needs to be frictionless for me. After "configure" and a couple "make distclean", the build process hangs at a specific

Re: [sage-devel] jupyter notebook vs jupyterlabs

Relevant discussion: https://groups.google.com/forum/?fromgroups#!topic/sage-devel/HRiG-Wfni18 On Saturday, October 24, 2020 at 12:51:08 PM UTC-7 dim...@gmail.com wrote: > Sage has not (yet) switched to jupyterlab, although there were various > ways to use jupyterlab with Sage posted here by

[sage-devel] Re: Jupyter notebook broken in 9.2.beta4

gain. I hope that works for you for now. But it is of course > not acceptable. > > Am Sonntag, 12. Juli 2020 02:26:02 UTC+2 schrieb Paul Masson: >> >> Just built a ticket based on 9.2.beta3 and the same problem occurs. >> >> On Saturday, July 11, 2020 at 4:09:56 PM UTC-7, Paul M

[sage-devel] Re: Jupyter notebook broken in 9.2.beta4

Just built a ticket based on 9.2.beta3 and the same problem occurs. On Saturday, July 11, 2020 at 4:09:56 PM UTC-7, Paul Masson wrote: > > After a successful incremental build from 9.2.beta2, trying to start a new > notebook results in the browser console error "Failed to

[sage-devel] Re: Jupyter notebook broken in 9.2.beta4

Just build a ticket based on 9.2.beta3 and the same problem occurs. On Saturday, July 11, 2020 at 4:09:56 PM UTC-7, Paul Masson wrote: > > After a successful incremental build from 9.2.beta2, trying to start a new > notebook results in the browser console error "Failed to

[sage-devel] Jupyter notebook broken in 9.2.beta4

After a successful incremental build from 9.2.beta2, trying to start a new notebook results in the browser console error "Failed to load resource: the server responded with a status of 404 (Not Found)" when trying to fetch Mathjax from http://localhost:/nbextensions/mathjax/MathJax.js. Has

[sage-devel] Error in Trac reports

Report 51 (Active tickets I participated in / by time) includes closed tickets. Since these are available in report 54 (Tickets I've participated in, including closed / by time) the former should be adjusted to exclude them. Who has access to fix this? Thanks. -- You received this message

[sage-devel] Trac server is crawling today...

Response is too slow to get anything done. Any idea why? Can somebody reboot something? -- 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] Re: Anomaly with several layered parametric plots 3d when using three.js

This is a basic problem with WebGL, which is what Three.js uses, as opposed to the canvas renderer in Jmol/JSmol. The current version of WebGL does not handle transparency very well, and there's not much we can do about that. Transparent objects in WebGL are treated as if they are located

[sage-devel] Question about Ubuntu patchbot

In the process of reviewing https://trac.sagemath.org/ticket/28130, I noticed that the Ubuntu patchbot fails to apply the commits of this ticket to 8.9.beta1. I created a clean branch of 8.9.beta1 and successfully merged the commits of this ticket without any issues, so what's up with the

Re: [sage-devel] Re: SageCell as back-end engine for the website

of data can we send to the server? On Wednesday, June 19, 2019 at 5:24:52 PM UTC-4, Paul Masson wrote: I put together some notes a while back on accessing SageCell as a web service. The results are returned as JSON and can be processed with JavaScript in the browser. That would

[sage-devel] Re: SageCell as back-end engine for the website

I put together some notes a while back on accessing SageCell as a web service. The results are returned as JSON and can be processed with JavaScript in the browser. That would be the simplest way

[sage-devel] Re: Poll: set online=True as the default for threejs viewer

The CDN fallback only applies to IPython/Jupyter notebooks, not plots generated at the command line. Notebooks need to be run in a local server, and the local server will always know how to find its files. The fallback will only be activated if the notebook is moved to a remote location, and

Re: [sage-devel] OSX: pip build failure. zlib dependancy ?

I can confirm that this fixes the issue for a completely clean build with macOS 10.14.3, but not on the first run. Takes a couple attempts for everything to build properly. On Thursday, March 7, 2019 at 2:54:08 AM UTC-8, Andrew wrote: > > Although I have not had this problem myself, zlib seems

[sage-devel] Re: help required for debugging on apple

Complete traceback, if it helps: File "src/sage/symbolic/expression.pyx", line 3537, in sage.symbolic.expression.Expression._cmp_ Failed example: RealSet((0, pi),[pi, pi],(pi,4)) Exception raised: Traceback (most recent call last): File

[sage-devel] Re: Name symbolic expressions

Nils, this is a most excellent answer. Coming to Sage from Mathematica, I continue to be puzzled by the various ways functions are handled in Sage, so thanks! This is a topic that has not yet been well documented. The only thing I have found close to it is a description of problems that can

[sage-devel] Re: git trac try

The documentation https://github.com/sagemath/git-trac-command at say that it creates a detached HEAD merge of the ticket and the develop branch. Since that was written by Volker, perhaps he could provide more information. On Thursday, March 9, 2017 at 1:28:57 AM UTC-8, Eric Gourgoulhon wrote:

[sage-devel] git trac try

For those of you like me who didn't know about this, git trac try is a fast way to review tickets without having to build older versions. git trac try automatically merges the current develop branch with only the changes on a ticket into a temporary branch. If you've already built the current

[sage-devel] Re: Bug report: Incorrect json representation for graphics.

On Wednesday, January 25, 2017 at 2:47:44 AM UTC-8, Frédéric Chapoton wrote: > > I am not sure that this json is sent to jmol at all. > The current implementation of Jmol does not use JSON -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] Re: Can't run binaries

If you have Anaconda installed, then remove any references it added to your $PATH variable. They create a conflict with Sage. On Tuesday, January 17, 2017 at 7:09:49 AM UTC-8, Sarfo wrote: > > Hello, > > I have been trying to run a local copy of sagemath from a binary I > downloaded after

[sage-devel] Re: SageManifolds 1.0 in Sage 7.5 and development workflow

Eric, it seems to me that this is now an area in which SageMath is ahead of Mathematica, and you are to be congratulated for that. Given that Wolfram is a physicist, I've never understood why there is no native support in Mathematica for general relativity calculations. Have you considered

Re: [sage-devel] Re: threejs as standard package

On Sunday, January 1, 2017 at 6:18:24 PM UTC-8, Paul Masson wrote: > > On Sunday, January 1, 2017 at 5:33:31 PM UTC-8, Andrey Novoseltsev wrote: >> >> Trying to get back to threejs: >> >> - it is apparently possible to use HTTPS for rawgit.com and it has a CDN

Re: [sage-devel] Re: threejs as standard package

On Sunday, January 1, 2017 at 5:33:31 PM UTC-8, Andrey Novoseltsev wrote: > > Trying to get back to threejs: > > - it is apparently possible to use HTTPS for rawgit.com and it has a CDN > which we actually must use to avoid being blocked > Sorry for some confusion I've created: I was sure I had

[sage-devel] Re: threejs as standard package

On Wednesday, December 28, 2016 at 3:47:53 PM UTC-8, Andrey Novoseltsev wrote: > > On Tuesday, 27 December 2016 15:34:51 UTC-7, Paul Masson wrote: >> >> I'm very much in favor of making Three.js a standard package, with the >> following caveats: >> >> 1) As

[sage-devel] Re: threejs as standard package

I'm very much in favor of making Three.js a standard package, with the following caveats: 1) As of r80 the Three.js library has been reorganized to use ES6 Modules. There is little point in asking people to download the entire library (even with examples excluded as in the current optional

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

On Saturday, December 3, 2016 at 2:30:36 PM UTC-8, William wrote: > > On Sat, Dec 3, 2016 at 2:28 PM, Paul Masson <paulm...@comcast.net > > wrote: > > There's apparently no good way in general to test whether the scene is > > unchanged. This is a known issue:

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

wrote: > > Well if the scene is static, the controls didn't change, and the canvas > size didnt't change then your callback in requestAnimationFram should just > do nothing instead of repainting the unchanged scene, right? > > > > On Saturday, December 3, 2016 at 9:46:50 PM

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

On Friday, December 2, 2016 at 11:47:40 PM UTC-8, tdumont wrote: > > > But why is three.js consuming cpu when the browser shouls have nothing > to do ? (no interaction). > There is a rendering loop that runs continuously to call requestAnimationFram(). This is a standard technique for

[sage-devel] Re: three.js on 7.5 beta 5: cpu...

Three.js performance is highly dependent on how the browser interacts with available graphics hardware. Chrome is the browser of choice for Three.js developers, but Firefox has made great improvements in the last couple years. If you're using the latest version of Firefox, then the bottleneck

[sage-devel] Current Maxima version

The version of Maxima that ships with Sage is 5.35.1 from December 2014, while the most recent version is 5.38.1 from May 2016. Is there a compelling reason not to upgrade this package? Surely some of the Maxima bug fixes will be relevant to Sage. -- You received this message because you are

[sage-devel] Re: Building 7.4.beta5 after building 7.5 betas

On Monday, November 14, 2016 at 3:51:49 PM UTC-8, Dima Pasechnik wrote: > > Did you have a pressing need to build an old branch? > I'd normally first rebase over the latest beta, and then build. > What do you mean by "rebase" precisely? Just merging the current develop branch or something else?

[sage-devel] Building 7.4.beta5 after building 7.5 betas

I'm running into an problem that after building 7.5.beta1 or 7.5.beta2, building a branch based on 7.4.beta5 fails for two packages: cysignals-1.1.1 and mistune-0.7.3. The only way I've found around it so far is to run make dist-clean && make but that takes more time than should be necessary.

[sage-devel] Errors from importing abs

Since abs is declared in functions/other.py as an explicit alias of abs_symbolic, I figured it wouldn't hurt to import if from that file but on https://trac.sagemath.org/ticket/21657 it leads to a variety of failed doctests. Some of these are coercion errors and others are more severe. I'd

Re: [sage-devel] Building Sage 7.4 final release on OS X El Capitan

the problem. Is the fix from Trac 21672 supposed to solve the problem for existing copies or only a pristine one? On Monday, November 7, 2016 at 2:44:43 AM UTC-8, Jeroen Demeyer wrote: > > On 2016-11-03 20:40, Paul Masson wrote: > > OSError: [Errno 2] No such file or directory: > >

Re: [sage-devel] Building Sage 7.4 final release on OS X El Capitan

.egg. On Wednesday, November 2, 2016 at 8:01:40 PM UTC-7, François wrote: > > It is probably not limited to El Capitan it would have been useful to get > some more details. > > Francois > > On 3/11/2016, at 2:07 PM, Paul Masson <paulm...@comcast.net > > wrote: >

[sage-devel] Building Sage 7.4 final release on OS X El Capitan

I had difficulty over the last couple days getting Sage 7.4 to build. Something like ten packages would fail to build, but not always the same ones. It finally occurred to me that there might be some race condition going on. Sure enough, running make without multiple jobs solved the problem.

[sage-devel] Re: doc.sagemath.org gone from google

: > > > > On Wednesday, October 19, 2016 at 6:24:17 PM UTC-4, Paul Masson wrote: >> >> In case no one else has noticed, doc.sagemath.org is now showing up in >> Google searches, including the link that initiated this thread. >> >> Google taketh away, and Go

[sage-devel] Re: doc.sagemath.org gone from google

In case no one else has noticed, doc.sagemath.org is now showing up in Google searches, including the link that initiated this thread. Google taketh away, and Google giveth back. On Sunday, August 7, 2016 at 8:25:56 AM UTC-7, William wrote: > > I'm googling for links to the sage reference

[sage-devel] Re: OS X testers needed

OS X 10.11.6 El Capitan: -- All tests passed! -- Total time for all tests: 5.2 seconds cpu time: 9.8 seconds cumulative wall time: 10.7 seconds On

Re: [sage-devel] Sage cells in interact wiki

I copied the generated source from a couple pages to an empty file and added a link to the SageMathCell script, https://sagecell.sagemath.org/static/embedded_sagecell.js";> and the interacts run (albeit with numerous deprecation errors). There is no problem with the SageMathCell

[sage-devel] Re: error building sagelib-7.4.beta4

Javier, this beta builds for me on El Capitan. What exact steps did you take to build Sage? On Thursday, September 15, 2016 at 9:29:12 AM UTC-7, jhonrubia6 wrote: > > hardware is macbook air and OS version is OS 10.11.6 > > El jueves, 15 de septiembre de 2016, 18:28:04 (UTC+2), jhonrubia6

Re: [sage-devel] Re: sage -br rebuilds things that were not changed

> But a Sage-installed ccache should also "just work". Jeroen, could you elaborate on this? How does one use ccache most simply with Sage? If this is currently the only way to speed up rebuilding when switching between branches, then I would like to add a concise description to the

[sage-devel] Re: 404 in Sage Installation Guide

Ticket to address this issue: https://trac.sagemath.org/ticket/21468 I used the text from the intermediate README file (with corrections) for the description of URL to the wiki. I also updated the only other URL in the SageMath repository pointing to sagemath.org/mirror/. On Saturday,

Re: [sage-devel] sage -br rebuilds things that were not changed

+1 That would save on time and confusion. On Friday, September 9, 2016 at 3:20:54 PM UTC-7, William wrote: > > On Fri, Sep 9, 2016 at 3:08 PM, Volker Braun > wrote: > > Whenever you switch to a branch with a different working set you change > > timestamps of modified

Re: [sage-devel] sage -br rebuilds things that were not changed

recythonizing be necessary when only changing the same file on the same branch? Thanks. On Friday, September 9, 2016 at 2:48:09 PM UTC-7, Jeroen Demeyer wrote: > > On 2016-09-09 23:34, Paul Masson wrote: > > I'm a bit confused by your answer, because I've been seeing the same > >

Re: [sage-devel] sage -br rebuilds things that were not changed

I'm a bit confused by your answer, because I've been seeing the same sort of behavior. For the last week I've been rebuilding a branch based on 7.4.beta2. With minor changes to one file, sage -b has been running very quickly. Today I made one minor change and the recythonizing kicked in. In

[sage-devel] Re: 404 in Sage Installation Guide

There does not appear to be a "README.txt" file for Windows installation in either the main SageMath repository or the website repository. If such a file ever existed, it's long gone. I even checked at archive.org for a backup copy, but since the robots.txt file has been blocking the /mirror/

[sage-devel] Plotting cot() fails in Sage 7.2 and 7.3

A simple plot of the cotangent function has been failing since version 7.2. I opened a Trac ticket for this a week ago: https://trac.sagemath.org/ticket/21365 The plotting method reports that it is unable to convert a complex to float for this function, even though the functional values look

[sage-devel] Bug (?) in multigraphs' plot

Definite bug: https://trac.sagemath.org/ticket/21370 -- 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

[sage-devel] Re: Problem retrieving a (positively reviewed) ticket

I tried again after I read that he rebooted the server, and once again just now. Same problem before and after rebooting. On Saturday, August 20, 2016 at 6:19:37 PM UTC-7, leif wrote: > > Paul Masson wrote: > > Getting the same error for https://trac.sagemath.org/ticket/21299 >

[sage-devel] Re: Problem retrieving a (positively reviewed) ticket

Getting the same error for https://trac.sagemath.org/ticket/21299 -- 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

[sage-devel] Re: doc.sagemath.org gone from google

Harald got access to the server hosting combinat.sagemath.org and added a server-side redirect to the corresponding documents on doc.sagemath.org. Hopefully that will speed up the indexing by Google of the new documentation location. On Sunday, August 7, 2016 at 8:25:56 AM UTC-7, William

Re: [sage-devel] Re: Trac notifications again

Erik, I receive closure notices and I'm not an admin. I also configured my preferences to receive everything but my own changes. -- 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,

[sage-devel] Re: doc.sagemath.org gone from google

As I understand them canonical URLs distinguish between the same content accessed through different URL forms. Currently Google thinks the documentation is mostly located at www.sagemath.org/doc/ while we want it to appear at

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

Running "make" under WSL for Sage 7.2.rc2 consistently hangs for me at this line: checking whether rename honors trailing slash on source... Could that be related to limits you mention or is it some other error? On Wednesday, August 3, 2016 at 6:44:56 AM UTC-7, Bill Hart wrote: > > There are

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Success! Many thanks to all who contributed. On Tuesday, July 26, 2016 at 1:19:55 PM UTC-7, Paul Masson wrote: > > The error message here led me to look at the "prompt_toolkit" package. > That directory is empty, as is one for "wcwidth". Removing both folders >

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

either by hand or via "git clean -fdx" > (the latter will throw away everything that isn't checked in). > > > > On Tuesday, July 26, 2016 at 9:55:48 PM UTC+2, Paul Masson wrote: >> >> Running "configure" resulted in a makefile that terminates at the

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

quot;wcwidth" aren't part of either the current master or develop branch. Could they have wandered in from some old Trac ticket I reviewed? On Tuesday, July 26, 2016 at 12:55:48 PM UTC-7, Paul Masson wrote: > > Running "configure" resulted in a makefile that terminates at

[sage-devel] Re: Trac attachment limit

What about a "packages" repository on GitHub just to store files? On Tuesday, July 26, 2016 at 12:07:45 AM UTC-7, Samuel Lelievre wrote: > > Maybe we could create packages.sagemath.org? > > 2016-07-25 21:33:39 UTC+2, Andrey Novoseltsev: > > > Creating my own site just for the sake of posting a

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

uot; is missing. "/Users/Masson/Downloads/GitHub/sage/build/pkgs/prompt_toolkit/type" is missing. checking that generated files are newer than configure... done configure: creating ./config.status On Tuesday, July 26, 2016 at 6:31:36 AM UTC-7, leif wrote: > > Paul Masson wrote

Re: [sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

On Tuesday, July 26, 2016 at 6:25:12 AM UTC-7, Jeroen Demeyer wrote: > > Got it! Your Makefile is corrupted, see this part: > > [...] > inst_pkgconf = $(INST)/pkgconf-0.9.7 > inst_pkgconfig = $(INST)/pkgconfig-1.1.0 > inst_planarity = $(INST)/planarity-2.2.0 > inst_plantri =

Re: [sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

MacBook-Retina:~ Masson$ make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for

[sage-devel] Incorrect links to external references in doc build

This Trac ticket looks related: https://trac.sagemath.org/ticket/21044 -- 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

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

uld include a version of Python. Mine has version > 2.7.10, dating from last December, in /usr/bin. If yours is missing, maybe > your PATH is wrong or maybe your Xcode installation is broken somehow. > > > > On Monday, July 25, 2016 at 9:06:35 PM UTC-7, Paul Masson wrote: >> &g

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

at 8:26:25 PM UTC-7, leif wrote: > > Paul Masson wrote: > > Ran make again without specifying any jobs, which I understand to be the > > same as specifying one job. Same error from Atlas this time as well. > > Here's the contents of that log: > > > > Foun

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

is written in Python, but the Python package is not yet installed in Sage. You should add $(PYTHON) as dependency in build/pkgs/atlas/dependencies On Monday, July 25, 2016 at 4:47:06 PM UTC-7, leif wrote: > > Paul Masson wrote: > > Sorry about that Leif. My bad. > > > > I

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

25, 2016 at 3:21:03 PM UTC-7, leif wrote: > > Paul Masson wrote: > > Most recent update applied: running OS X 10.11.6 > > Paul, you really shouldn't post install.log of *parallel* builds (at > least not before Sage 7.3.*; "master" is of course 7.2), but better

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

t 12:38:58 PM UTC-7, Paul Masson wrote: > > Most recent update applied: running OS X 10.11.6 > > Install log: https://drive.google.com/open?id=0B9H_P15GCK5yME43Sjk2bmFZSmM > > On Sunday, July 24, 2016 at 11:54:06 PM UTC-7, Volker Braun wrote: >> >> Whats in the logs?

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

> On Monday, July 25, 2016 at 4:44:21 AM UTC+2, Paul Masson wrote: >> >> In an effort to get past a recurring issue for reviewing Trac #21034, I >> did "make distclean" followed by "make". Now I am no longer able to build >> Sage as I have been doing

[sage-devel] No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

In an effort to get past a recurring issue for reviewing Trac #21034, I did "make distclean" followed by "make". Now I am no longer able to build Sage as I have been doing for the last couple months, either the master or develop branch. This is the error message I keep getting: * package:

[sage-devel] Re: Plotting text doesn't disappear for axes inside the text range

Daniel, there is an additional option for Text objects that does what you want. Add the keyword argument "clip=True" to your text and it will be clipped according to the min/max settings. This option is not yet in the documentation, so I've created a ticket to take care of that:

[sage-devel] Re: Current best practice for LaTeX of function names

Ralf, I was looking at a notebook created some time ago when I reported this behavior. After reevaluating the cell containing an elliptic integral, the LaTeX formatting was indeed rendered. The problem is now just with SageMathCell so I've opened an issue on GitHub:

[sage-devel] Trac error: branch shows entire file deleted

When I look at the branch for ticket #15134 it show the entire file hyperbolic.py deleted. For Travis it shows just the changes from the existing commits as expected. He also says the error occurs sometimes. Any idea what causes this? It's a bit disconcerting to see the contents of an entire

[sage-devel] Re: Current best practice for LaTeX of function names

Ralf, I'm finally getting ready to add/standardize LaTeX names for special functions. I wanted to start with elliptic integrals but see that latex_name or _print_latex_ are already defined for all of them. The LaTeX formatting shows at the command line but does not get rendered in notebooks or

[sage-devel] Re: Git repository should have Sage versions as branches not tags

dated). > > The bot is maintained by Robert Bradshaw, he might be able to comment more. > See https://wiki.sagemath.org/Infrastructure > > > Le dimanche 17 juillet 2016 23:06:37 UTC+2, Paul Masson a écrit : >> >> Thanks. >> >> Another question: who closes Iss

[sage-devel] Re: Git repository should have Sage versions as branches not tags

Thanks. Another question: who closes Issues and Pull Requests on Github that have been marked ready for closure? On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote: > > done > > On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote: >> >> The m

[sage-devel] Re: Git repository should have Sage versions as branches not tags

The mirror actually has three branches. This one hasn't been touched in over a year: https://github.com/sagemath/sage/tree/module-list-cleanup Shouldn't it be removed at some point? On Wednesday, July 13, 2016 at 6:53:21 PM UTC-7, John Phamlore wrote: > > The mirror at > >

[sage-devel] Re: branch is not clickable

I just pushed to #9654 and the commit is not appearing. On a second push Git said everything is up to date, so I'm assuming the commit is there but not showing up in the web interface. What's up? On Tuesday, July 5, 2016 at 1:15:55 PM UTC-7, Dima Pasechnik wrote: > > I see errors like

[sage-devel] Re: [sage-edu] Viewpoint Article in Math Intelligencer on open texts

https://moscow.sci-hub.cc/12ca465033b407001af9d921b2c7f5fa/hefferon2016.pdf -- 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] Re: trac mails are back on

Just got this error when saving changes to #18889: closeWarning: The change has been saved, but an error occurred while sending notifications: expected string or buffer Important? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

[sage-devel] Re: Current best practice for LaTeX of function names

Hey Ralf, I'm trying to understand this behavior: sage: latex(beta(x,x)) {\rm B}\left(x, x\right) Since there are currently no LaTeX definitions of any sort for the beta function, where is the capital "B" coming from? It's a minor question but it's bugging me. Thanks. On Wednesday, June 15,

[sage-devel] Re: Numerical errors in gegenbauer() for float argument

t; On Thursday, June 23, 2016 at 1:39:43 AM UTC+2, Paul Masson wrote: >> >> This series of values is correct for integer arguments: >> >> >> sage: gegenbauer(2,1,x) >> >> 4*x^2 - 1 >> >> sage: gegenbauer(2,1,0) >> >> -1 >>

[sage-devel] Numerical errors in gegenbauer() for float argument

This series of values is correct for integer arguments: sage: gegenbauer(2,1,x) 4*x^2 - 1 sage: gegenbauer(2,1,0) -1 sage: gegenbauer(2,1,1) 3 sage: gegenbauer(2,1,2) 15 But nonzero floats give wrong answers: sage: gegenbauer(2,1,1.) 0.500 sage: gegenbauer(2,1,2.)

[sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

Since no one has said this yet, a big thank you to Erik and everyone else who helped get the Trac server to its new home! On Monday, June 20, 2016 at 8:18:49 AM UTC-7, Erik Bray wrote: > > Hi all, > > As decided toward the end of another recent thread [1] I willl be > taking down the server at

[sage-devel] Re: What is the best time for Trac downtime?

I agree with Dima: working infrastructure takes top priority. Erik, on the new server I'm seeing this error on several tickets: *Trac detected an internal error:* OSError: [Errno 2] No such file or directory: '/tmp/tmp9sMYW3' There was an internal error in Trac. It is recommended that you

Re: [sage-devel] Re: Evaluation of beta() in Sage 7.2

emath.org/ticket/12521 > > On Tuesday, June 14, 2016 at 8:51:26 PM UTC+2, Paul Masson wrote: >> >> Ralf, my original input for the beta function has one negative argument. >> That returns "NaN" for both Sage 7.2 and 7.3beta4. >> >> It appears

Re: [sage-devel] trac slow/unresponsive

No change for me. Still can't modify a ticket. Server not responding when submit change. On Wednesday, June 15, 2016 at 3:05:58 PM UTC-7, William wrote: > > On Wed, Jun 15, 2016 at 4:45 PM, Paul Masson <paulm...@comcast.net > > wrote: > > Is there a firm plan in place

Re: [sage-devel] trac slow/unresponsive

Is there a firm plan in place to move this database to a hosting service? It's discouraging to spend time trying to help, only to run into machine issues. On Wednesday, June 15, 2016 at 12:15:45 PM UTC-7, William wrote: > > I can restart the machine if you guys want... > > > On Wed, Jun 15,

[sage-devel] Re: Current best practice for LaTeX of function names

A good example is elliptic integrals. Complete elliptic integrals have a single letter as the function name, while the incomplete integrals require specifying the modulus or parameter. Since SageMath uses the parameter, a typical format for incomplete integrals has the argument separated from

Re: [sage-devel] trac slow/unresponsive

lliam > > On Wed, Jun 15, 2016 at 2:52 PM, Paul Masson <paulm...@comcast.net > > wrote: > > Similar for me in San Francisco, except can't make any changes. Server > keeps > > timing out. > > > > > > On Wednesday, June 15, 2016 at 11:49:08 AM UTC

Re: [sage-devel] trac slow/unresponsive

Similar for me in San Francisco, except can't make any changes. Server keeps timing out. On Wednesday, June 15, 2016 at 11:49:08 AM UTC-7, Jeroen Demeyer wrote: > > Currently, this is happening for me right now. Read-only access is still > mostly working, but changing anything takes forever. >

[sage-devel] Re: Current best practice for LaTeX of function names

is > > > On Tuesday, June 14, 2016 at 7:04:00 PM UTC-5, Kwankyu Lee wrote: >> >> It is _latex_(self) according to the developer manual >> >> >> http://doc.sagemath.org/html/en/developer/coding_in_python.html#latex-representation >> >> On Wednesday

[sage-devel] Current best practice for LaTeX of function names

I'd like to add LaTeX support to special functions that do not yet have it. Before I start, I'd like to know what the current recommendation is for such support. >From reading source code, it appears that adding a keyword argument latex_name to the function initialization is equivalent to

  1   2   >