[sage-devel] Re: unicode and pdf documentation build failure

2020-06-02 Thread 'Travis Scrimshaw' via sage-devel
Hi John, Thank you, that was precisely what I was looking for. I could not remember how to do that. Best, Travis On Wednesday, June 3, 2020 at 3:28:49 PM UTC+10, John H Palmieri wrote: > > Hi Travis, > > Can you add a command to `latex_elements['preamble']` in > src/sage/docs/conf.py`? There

[sage-devel] Re: unicode and pdf documentation build failure

2020-06-02 Thread John H Palmieri
Hi Travis, Can you add a command to `latex_elements['preamble']` in src/sage/docs/conf.py`? There are a lot of unicode characters defined there already. \DeclareUnicodeCharacter{26AC}{\circ} or something like that? On Tuesday, June 2, 2020 at 8:24:52 PM UTC-7, Travis Scrimshaw wrote: > > Hi e

[sage-devel] unicode and pdf documentation build failure

2020-06-02 Thread 'Travis Scrimshaw' via sage-devel
Hi everyone, I have a patch with some unicode that uses a character (U+26AC, ⚬) that is not recognized by the pdf docbuild. Is there some way I can add an option for the pdf docbuilder to translate this unicode character into a latex symbol so the PDF doc will build? Or is the best option jus

Re: [sage-devel] Re: line length in docstring and tests

2020-06-02 Thread Nils Bruin
On Tuesday, June 2, 2020 at 10:13:55 AM UTC-7, Michael Orlitzky wrote: > > > You shouldn't force yourself to stick to 80 characters when there's a > technical reason for the line to be longer, but the argument for the > 80-character limit is not some fairy tale about punch cards or > PDP-11/VAX

Re: [sage-devel] Re: line length in docstring and tests

2020-06-02 Thread 'Reimundo Heluani' via sage-devel
On Jun 02, Michael Orlitzky wrote: On 6/2/20 9:52 AM, Volker Braun wrote: I'm with Linus in that the 80 characters limit is an anachronism thats too restrictive in a time and age where large high-resolution displays are ubiqitous. There certainly is a "too long" somewhere but its more in the 100

Re: [sage-devel] Re: line length in docstring and tests

2020-06-02 Thread Michael Orlitzky
On 6/2/20 9:52 AM, Volker Braun wrote: > I'm with Linus in that the 80 characters limit is an anachronism thats > too restrictive in a time and age where large high-resolution displays > are ubiqitous. There certainly is a "too long" somewhere but its more in > the 100-character region. > > https:

[sage-devel] Re: Mutliprocessing for Matrix Computations?

2020-06-02 Thread Marc Mezzarobba
Michael Jung wrote: > Ah, interesting. Do you have some literature/references for me? Among the standard references, Chapter 5 of *Modern Computer Algebra* by von zur Gathen & Gerhard discusses the basic evaluation-interpolation algorithm for computing the determinant of polynomial matrices in s

[sage-devel] Re: line length in docstring and tests

2020-06-02 Thread Volker Braun
I'm with Linus in that the 80 characters limit is an anachronism thats too restrictive in a time and age where large high-resolution displays are ubiqitous. There certainly is a "too long" somewhere but its more in the 100-character region. https://git.kernel.org/pub/scm/linux/kernel/git/torval

[sage-devel] Re: New Python version requirement for Sage?

2020-06-02 Thread Volker Braun
Thats true, I'll fix it On Monday, June 1, 2020 at 11:08:36 PM UTC+2, Jonathan Kliem wrote: > > At the moment we are guessing that kucalc buildbot runs with ./configure > --with-python=2, because this will lead to exactly this error message (and > it really is the only way that this error messa

Re: [sage-devel] Problem building R on 10.15.5 with homebrew

2020-06-02 Thread Dima Pasechnik
Hi Zach, On Tue, Jun 2, 2020 at 2:39 AM Zachary Scherr wrote: > >It looks like both were already linked but I ended up reinstalling them > and everything worked, thank you so much. > > In general, do you recommend installing libraries like flint from > sagemath/homebrew-science before build