[sage-devel] Re: show() method for all sage objects

Le lundi 20 mai 2019 07:55:30 UTC+2, Kwankyu Lee a écrit : > > . Moreover many sage objects currently are displayed broken if typeset. > In that case, a solution could be to introduce a new class, TypesetSageObject, say, to implement _repr_latex_() in it and to make Sage objects that can be

[sage-devel] Re: show() method for all sage objects

Le dimanche 19 mai 2019 10:48:23 UTC+2, Volker Braun a écrit : > > > In general, I would lean more on the side of reasonable defaults (e.g. why > is %display typeset not the default in the notebook, its easier for power > users to turn it off than for novices to turn it on) than a proliferation

[sage-devel] Re: Wrong polynomial factoring

Indeed, the factor function of Sage is terribly buggy at the moment, see https://trac.sagemath.org/ticket/27304 The issue you report seems to have been triggered by https://trac.sagemath.org/ticket/23835 (merged in Sage 8.4.beta3) as well, since we have a correct result in Sage 8.3:

[sage-devel] Re: Characteristic Classes - Implement Vector Bundles?

Hi, Le jeudi 2 mai 2019 13:12:43 UTC+2, Michael Jung a écrit : > > Hey there, > for the next step of implementing characteristic classes, I'd like to > implement abstract vector bundles. > > 1) Do you agree? > Having vector bundles would be nice! But what do you mean by *abstract* vector

Re: [sage-devel] Trac down?

Le mercredi 24 avril 2019 19:20:50 UTC+2, Dima Pasechnik a écrit : > > OK, all should be back to normal. If not, please shout... > > Thanks DIma! Everything is fine now. Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Trac down?

Hi, It seems the page https://trac.sagemath.org/ is not responding. It was OK an hour ago or so. One can perform "git pull" from Trac though (i.e. git://trac.sagemath.org/ is up). Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] Re: Scalar Field in Diff Form Algebra? Check fails!

Le dimanche 14 avril 2019 10:38:40 UTC+2, Michael Jung a écrit : > > I apologize. The issue was there before (tested on sage 8.6). I open a > ticket. Agreed? > Thanks for the report. I've already opened https://trac.sagemath.org/ticket/27658 Eric. > However, how are beta issues managed? >

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

[sage-devel] Black hole image computed with Sage

Hi All, As you may have heard in the news, the Event Horizon Telescope collaboration will release tomorrow the very first observed image of the close vicinity of a black hole: https://eventhorizontelescope.org/blog/media-advisory-first-results-event-horizon-telescope-be-presented-april-10th

Re: [sage-devel] Re: Characteristic classes on manifolds

Le mercredi 3 avril 2019 13:38:17 UTC+2, Michael Jung a écrit : > > Okay, the code has been uploaded. :) > > Thanks! I found the reason. I am answering on the ticket. Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Re: Characteristic classes on manifolds

Le mardi 2 avril 2019 22:54:51 UTC+2, Michael Jung a écrit : > > > All fine, except the very last line. The coercions are working quite well > so far - without any errors. Yet, what might explain the very different > results? Can you give me a first hint, though not seeing the code? > Well it's

[sage-devel] Re: Characteristic classes on manifolds

that your code is fully python3 compatible cf. https://wiki.sagemath.org/Python3-compatible%20code since SageMath migration to python3 is getting close: https://trac.sagemath.org/ticket/26212 Am Sonntag, 31. März 2019 11:40:01 UTC+2 schrieb Eric Gourgoulhon: >> >> Hi, >> >> L

[sage-devel] Re: Characteristic classes on manifolds

Hi, Le samedi 30 mars 2019 19:03:27 UTC+1, MJ a écrit : > > My dear developers, > right now, I'm working on my master thesis and my task is to implement > characteristic classes (of the tangent bdl. of a manifold), such as the > A-genus, into Sage. The implementation shall be based > upon this

Re: [sage-devel] Re: Problem with wedge of unnamed diff forms on non-parall. mfds

public/manifolds/bug_wedge_unnamed_trac27576 ./sage -b NB: this is fast and easy only if you have SageMath *8.7* installed Le dimanche 31 mars 2019 00:43:16 UTC+1, Eric Gourgoulhon a écrit : > Thanks MJ for reporting the bug and opening the ticket. > It is fixed in the ticket bran

Re: [sage-devel] Re: Problem with wedge of unnamed diff forms on non-parall. mfds

Hi, Thanks MJ for reporting the bug and opening the ticket. It is fixed in the ticket branch now. Nils: yes I banged my head on the desk a couple of times :-) Best wishes, Eric. Le samedi 30 mars 2019 20:49:37 UTC+1, MJ a écrit : > > Yes, of course. I'm just too impatient for tasks like

[sage-devel] Re: How would you like your parallel linear algebra ?

PS: an example of use of Parallelism() is http://doc.sagemath.org/html/en/reference/manifolds/sage/manifolds/differentiable/affine_connection.html#sage.manifolds.differentiable.affine_connection.AffineConnection.riemann Le vendredi 22 mars 2019 14:36:10 UTC+1, Eric Gourgoulhon a écrit : > &

[sage-devel] Re: How would you like your parallel linear algebra ?

Hi, Regarding your question 3: Le vendredi 22 mars 2019 11:15:04 UTC+1, Clement Pernet a écrit : > > 3. What interface do we want for the sage user who wants to > >3a switch between sequential and parallel, > >3b specify the number of cores to be used ? > > Should there be some kind

[sage-devel] Re: Error with Parallelism, case of nproc>1

The bug seems to be triggered by the use of a symbolic function (the one created by function('chi')). It is now tracked at https://trac.sagemath.org/ticket/27492 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

[sage-devel] Re: Error with Parallelism, case of nproc>1

Thanks for the report. I confirm the bug in Sage 8.7.beta7. What is strange is that ddChi seems a perfectly valid symbolic expression: sage: ddChi = ddChi.expand(); ddChi 2*diff(chi(r, theta, phi), r)/r + cos(theta)*diff(chi(r, theta, phi), theta )/(r^2*sin(theta)) + diff(chi(r, theta, phi),

[sage-devel] Regression in 3D plots in reference manual (Sage 8.7.beta7)

Hi, In Sage 8.7.beta7, all 3D plots in the html reference manual, like those of the 3D Graphics section , are generated with a square frame around them, with axes marks ranging from 0 to 500. This happens both

Re: [sage-devel] Re: Scalar field on manifold not completely initialized?

I've opened https://trac.sagemath.org/ticket/27475 to deal with this issue. -- 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

Re: [sage-devel] Regression in Jupyter notebook (Sage 8.7.beta7)

Le lundi 11 mars 2019 16:53:07 UTC+1, Jeroen Demeyer a écrit : > > On 2019-03-11 16:42, Eric Gourgoulhon wrote: > > Shall I open a ticket? > > Yes and please include the traceback. > OK, this is now https://trac.sagemath.org/ticket/27463 -- You received thi

[sage-devel] Regression in Jupyter notebook (Sage 8.7.beta7)

Hi, With Sage 8.6, it is possible to open directly a notebook file by sage -n jupyter file_name.ipynb With Sage 8.7.beta7 (python 2 version), the same command yields TypeError: coercing to Unicode: need string or buffer, int found With Sage 8.7.beta7 (python 3 version), this is OK. Since Sage

[sage-devel] Re: Scalar field on manifold not completely initialized?

Hi, Le vendredi 22 février 2019 21:33:38 UTC+1, Richard_L a écrit : > > I conclude there is something about the scalar field which is not being > defined until the .display() is executed. > Is this the intended behavior, or an oversight? > The issue is not related to scalar fields: it is

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

Just another data point: the option "online=True" is currently necessary to display threejs in Jupyter notebooks on CoCalc (without it, one gets just a blank). That said, I agree with the concerns expressed here about the silent access to internet and the user's privacy. Eric. -- You

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

Le lundi 11 février 2019 22:25:37 UTC+1, vdelecroix a écrit : > > > > > Basically, threejs needs two javascript files to run: three.min.js and > > OrbitControls.js > > If online=False (the current default), it searches for them in > > SAGE_HOME/local/share/threejs > > which is not available

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

gt; > > > On Tue, Feb 12, 2019 at 08:35:23AM +1300, François Bissey wrote: > >> I will formally vote for “True”. > >> > >> However I think the default should be "use online if available" and > fall back if not. > >> But that implies writing new co

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

Hi, As pointed out in the Free Computational Mathematics conference today, the default value of the "online" option of the threejs 3d viewer is False. This allows for the rendering without any internet connection, but it has the serious drawback to

[sage-devel] Re: python3 status report

Le mardi 29 janvier 2019 10:29:43 UTC+1, Samuel Lelievre a écrit : > > Sun 2019-01-27 14:23:08 UTC+1, Frédéric Chapoton: > > > > > > STATEMENT: I would to advocate that *every developer switch to python3 > NOW*. > > > > > > Please vote! > > Strong +1 from me. > > +1 from me too. Many, many

Re: [sage-devel] Re: Wrong solution/output for differential equation

Le mardi 22 janvier 2019 20:55:11 UTC+1, Thrash a écrit : > > Can someone please report it upstream? Or tell me how to do it? > > You should report it here: https://sourceforge.net/p/maxima/bugs/ Here is a recent example of bug report arising from a SageMath user:

Re: [sage-devel] Build error

Le dimanche 20 janvier 2019 11:25:36 UTC+1, Dima Pasechnik a écrit : > > > First of all, on a Linux system you almost never would need to build > Sage-supplied gfortran, it's much easier to install a system-wide gfortran > using the system's package manager. > See >

[sage-devel] Re: [sagemath-admins] Bad source tarballs for ipython-5.8.0 on some mirrors

Le vendredi 18 janvier 2019 16:23:23 UTC+1, Samuel Lelievre a écrit : > > I just wrote to the maintainers of the SageMath download mirror > at LIP6, Paris. > Btw, I've noticed that LIP6 does no longer appear (nor any French mirror...) in the list of mirrors for binaries:

[sage-devel] Re: [sagemath-admins] Bad source tarballs for ipython-5.8.0 on some mirrors

Hi, It turns out that 3 package source tarballs have incorrect checksums on www-ftp.lip6.fr: ipython_genutils-0.2.0.tar.gz jinja2-2.10.tar.gz ipython-5.8.0.tar.gz Copying to SAGE_ROOT/upstream tarballs downloaded from another mirror (mirror.koddos.net) for these three ones (only) lead to a

[sage-devel] Re: "COMPUTATIONAL MATHEMATICS WITH SAGEMATH"

Le jeudi 13 décembre 2018 04:48:20 UTC+1, kcrisman a écrit : > That's all great news, and especially thanks and congratulations to the > whole team who worked on both the French and English versions! > Indeed this book is excellent! Congratulations to the authors! Eric. -- You received

[sage-devel] Bug with symbolic functions

Hi, I've just been hit by a quite annoying bug, a minimal example of which is sage: r, b = var('r b', domain='real') sage: s = function('a', latex_name=r'\alpha')(r) sage: latex(s) \alpha\left(r\right) sage: latex(s.simplify()) a\left(r\right) sage: s - s.simplify() a(r) - a(r) sage:

[sage-devel] Re: sage Python3 build: sagenb problem

Hi, I had the same problem this morning, while performing the python3 build of Sage 8.5.beta1: [sagenb-1.1.0] Error installing package sagenb-1.1.0 The command was MAKE="make -j8" make build Running it a second time lead to a successful build though... Eric. -- You received this message

[sage-devel] Re: refresh the banner

+1 for the new banner! Eric. -- 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] Re: Make and html docs

Hi Jori, Le mardi 23 octobre 2018 12:50:59 UTC+2, Jori Mäntysalo a écrit : > > I just downloaded 8.4 and ran make. Makefile says "The default target > ("all") builds Sage and the whole (HTML) documentation.", but actually > plain "make" just compiled the binary, not docs. Can someone confirm

[sage-devel] Re: Is there a math alternative to range and interval?

Le jeudi 18 octobre 2018 14:13:33 UTC+2, Simon King a écrit : > > > Such as srange(i,j)? > > Btw, I've just noticed that in Python3-built Sage 8.4.rc1, srange returns a list. Shouldn't it return an iterator instead? Eric. -- You received this message because you are subscribed to the Google

[sage-devel] Re: Is there a math alternative to range and interval?

Hi, An alternative to Simon's answer is sage: [i.is_prime() for i in [1..9]] [False, True, True, False, True, False, True, False, False] Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

Re: [sage-devel] Cannot connect to trac

Thanks Dima and Erik for your prompt answers! It was indeed a local problem. Thanks to the link provided by Dima, I've found the answer by running SSH_AUTH_SOCK=0 ssh g...@trac.sagemath.org info This revealed that the file ~/.ssh/id_rsa had wrong permissions (readable by everybody). This

[sage-devel] Cannot connect to trac

Hi, I cannot push any commit to trac this morning since the authentication seems to fail: ssh g...@trac.sagemath.org info sign_and_send_pubkey: signing failed: agent refused operation g...@trac.sagemath.org: Permission denied (publickey). I've removed trac from ~/.ssh/known_hosts via

Re: [sage-devel] Re: Change (bug or feature?) in 3d plots illustrating the reference manual

Le lundi 17 septembre 2018 15:32:55 UTC+2, Eric Gourgoulhon a écrit : > > > > >> (for the HTML docs why not >> use threejs by default across the board?) >> > > Yes absolutely, but only after #22408 > <https://trac.sagemath.org/ticket/22408&

Re: [sage-devel] Re: Change (bug or feature?) in 3d plots illustrating the reference manual

Le lundi 17 septembre 2018 14:45:22 UTC+2, Erik Bray a écrit : > > > If there's something about the > Tachyon plots that's inferior to the Jmol plots, or at least > noticeably different, we should fix that IMHO the main thing that makes Tachyon plots inferior to Jmol ones is the lack of axes

[sage-devel] Re: Change (bug or feature?) in 3d plots illustrating the reference manual

Hi Volker, Le vendredi 14 septembre 2018 22:44:34 UTC+2, Volker Braun a écrit : > > I don't think there was a deliberate change. Rendering the jmol version > requires java, which is an external dependency. There was also a bug in > detecting java 10+ which is only fixed in Sage 8.4.beta4. The

[sage-devel] Change (bug or feature?) in 3d plots illustrating the reference manual

Hi, Between Sage 8.4.beta0 and 8.4.beta2, all 3d plots illustrating the reference manual, like in this section , have been changed to Tachyon-rendered images. Previously (in particular in Sage 8.3), they were png

[sage-devel] Re: Can't compile 8.4.beta3

Hi, >From your install.log file, we can see a message that could provide some hint: [pip-18.0] /usr/local/src/sage/local/bin/python3: No module named pip As Samuel said, it would be helpful to look at /usr/local/src/sage/logs/pkgs/pip-18.0.log. Eric. -- You received this message because

Re: [sage-devel] 3D plots in Jupyter notebook broken since Sage 8.4.beta0

Le mardi 28 août 2018 14:11:48 UTC+2, Erik Bray a écrit : > > > Do you know if we have any progress on the process of deprecating jmol? > > In principle, any progress should be reported in the ticket https://trac.sagemath.org/ticket/22408 As you can see, there hasn't been much progress

Re: [sage-devel] 3D plots in Jupyter notebook broken since Sage 8.4.beta0

Le lundi 27 août 2018 12:21:15 UTC+2, François Bissey a écrit : > > https://trac.sagemath.org/ticket/26114 should be in the next beta and fix > this issue. > > OK very good. Thanks! Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] 3D plots in Jupyter notebook broken since Sage 8.4.beta0

Hi, Since Sage 8.4.beta0, the default 3D viewer (Jmol) seems broken in Jupyter notebooks. For instance, typing sphere() results in a blank screen, with the following message in the console: [W 12:14:53.681 NotebookApp] 404 GET /nbextensions/jsmol/JSmol.min.js (127.0.0.1) 16.30ms referer=None

[sage-devel] Re: Enabling Merge Requests from GitLab

Hi, Le mardi 21 août 2018 10:43:19 UTC+2, Erik Bray a écrit : > > Why GitLab? In short, we felt it would likely be more acceptable to > most members of the Sage community; this was a feeling we had even > before the Microsoft's acquisition of GitHub was announced. First of > all, GitLab is

Re: [sage-devel] Parallelization issue on macOS

Le vendredi 17 août 2018 15:26:37 UTC+2, Erik Bray a écrit : > > On Fri, Aug 17, 2018 at 2:02 PM Eric Gourgoulhon > wrote: > > > > Btw, I would be curious to know whether the notebook > > > http://nbviewer.jupyter.org/github/sagemanifolds/SageManifol

Re: [sage-devel] Parallelization issue on macOS

Hi Erik, Le jeudi 16 août 2018 13:53:41 UTC+2, Erik Bray a écrit : > > Love how fork() is even more broken on OSX now than it is on Cygwin =_= > Btw, I would be curious to know whether the notebook

Re: [sage-devel] Parallelization issue on macOS

Hi Jeroen, Le jeudi 16 août 2018 10:27:37 UTC+2, Jeroen Demeyer a écrit : > > On 2018-08-15 17:46, Eric Gourgoulhon wrote: > > Various Sage users have reported on that parallelization of tensor field > > computations does not work on macOS. > > This might be https://

[sage-devel] Parallelization issue on macOS

Hi, Various Sage users have reported on that parallelization of tensor field computations does not work on macOS. The latest report, yesterday on sagemanifolds.list: https://sympa.obspm.fr/wws/arc/sagemanifolds.list/2018-08/msg3.html says that this example notebook

[sage-devel] Re: SM_Carter-Penrose_diag.ipynb

Hi, It looks very obscure and is certainly nothing that could be executed in > any version of SageMath (neither in command line nor in the notebook). > > Indeed it was not very clear... Aishen was actually referring to the Carter-Penrose diagram of the manifold examples

[sage-devel] Re: Poll about adopting matplotlib2 style for Sage graphics

Le vendredi 13 juillet 2018 02:38:09 UTC+2, Kwankyu Lee a écrit : > > I recommend you to examine the Sage documentation built with the patch of > #25799 before voting. > Note that "make" is not sufficient to regenerate the plots after the ticket branch is merged. One must run "make doc-clean"

[sage-devel] Re: Poll about adopting matplotlib2 style for Sage graphics

+1 for me. Best wishes, Eric. -- 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] Re: How parallel should @parallel be?

Le mercredi 11 juillet 2018 16:11:01 UTC+2, Julian Rüth a écrit : > > Thanks for the feedback so far. It seems that there are pros and cons to > all of the options. > > What about the following: We go with the somewhat random min(8, number of > threads) and print a warning once if "number of

Re: [sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage

HI, Le lundi 9 juillet 2018 12:53:24 UTC+2, Kwankyu Lee a écrit : > > Consulting > > https://matplotlib.org/users/dflt_style_changes.html > > we may keep specifically only the math font of the classic style by: > > mpl.rcParams['mathtext.fontset'] = 'cm' > mpl.rcParams['mathtext.rm'] = 'serif' >

[sage-devel] Re: Names of objects in sage

Note that in the Jupyter notebook, having set %display latex you can have both outputs: LaurentPolynomialRing(ZZ,'q') returns *Z*[q^{\pm 1}] while print(LaurentPolynomialRing(ZZ,'q')) returns Univariate Laurent Polynomial Ring in q over Integer Ring By the way, I would advocate that %display

[sage-devel] Re: Re; Symbolic matrix inverse still gives seg-fault, core-dump

Le mercredi 20 juin 2018 00:22:07 UTC+2, Nils Bruin a écrit : > > On Tuesday, June 19, 2018 at 2:30:46 PM UTC-7, Richard_L wrote: >> >> It would be useful if one could override Sage's default "domain:complex", >> at least until the Maxima fix comes through. >> >> One can:

[sage-devel] Re: Cloning Sage git hangs

Hi Victor, Usually I am using the github mirror instead of git.sagemath.org to perform a git clone, for it has a better bandwidth: git clone https://github.com/sagemath/sage.git I don't know if this can solve your problem. Best wishes, Eric. Le mercredi 23 mai 2018 00:13:25 UTC+2, Victor

Re: [sage-devel] New version of Windows installer--where best to announce?

Hi, Le samedi 19 mai 2018 13:48:52 UTC+2, Samuel Lelievre a écrit : > > > > Possibly related: why is this not on the Sage mirrors? clicking from > > sagemath.org on "Download -> Windows" I have access to the virtual box > > versions that are much less satisfactory than the cygwin one. > > Not

[sage-devel] Re: Missing Sage 8.2 binaries

Hi, There seems to be many failures on the buildbots: http://build.sagemath.org Eric. -- 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: Wrong result for definite integral of sin(x)*exp(I*x)

Hi, Indeed, this seems a bug in Sage. Note that both SymPy and Giac return the correct answer: sage: integrate(sin(x)*exp(I*x), x, -pi, 0) 3/2*I*pi sage: integrate(sin(x)*exp(I*x), x, -pi, 0, algorithm='sympy') 1/2*I*pi sage: integrate(sin(x)*exp(I*x), x, -pi, 0, algorithm='giac') 1/2*I*pi

[sage-devel] Re: Jupyter Notebook, Sage, and LaTeX not talking like they should

Hi, This is a known issue, already reported in Trac #23330 . Unfortunately, there is no fix yet... Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

[sage-devel] Re: Possible bug in gen_legendre_P (associated Legendre polynomials)

Hi, Le mardi 27 mars 2018 14:46:52 UTC+2, Ralf Stephan a écrit : > > > I think it will suffice for now to put the fact in the documentation. > I am afraid this is not sufficient: a consequence of this bug is that Sage gives a silly answer for something as elementary as the spherical harmonic

[sage-devel] Re: 8.2.rc0 - banner change ?

Thanks for reporting. This is handled by https://trac.sagemath.org/ticket/25056 Best wishes, Eric. -- 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: How much do we support the casual user

Hi Simon, hi Erik, Le mardi 27 mars 2018 21:09:08 UTC+2, Simon King a écrit : > > Hi Erik, > > On 2018-03-27, Erik Bray wrote: > > What about adding an optional argument to the is_prime() > > method--something like a.is_prime(as_element_of=ZZ). It's kind of a > > wordy

[sage-devel] Re: Shortcoming in Jupyter Notebook w.r.t. latex in help

Hi, Another issue involving the Jupyter notebook and LaTeX is that typeset outputs, which are correctly rendered with MathJax in the browser, are no longer typeset when exporting the notebook to pdf: https://trac.sagemath.org/ticket/23330 Probably the two issues are not related (or maybe they

[sage-devel] Elementary vector calculus with Sage

Hi, After demands from users (see e.g. https://ask.sagemath.org/question/40792/div-grad-and-curl-once-again/ and https://ask.sagemath.org/question/10104/gradient-divergence-curl-and-vector-products/) and a first attempt (see ticket #3021 ), a proposal

[sage-devel] Re: Git push issues

Le mardi 6 mars 2018 16:31:56 UTC+1, Eric Gourgoulhon a écrit : > > > The target on trac does not seem correct; the syntax of the push command > should be > > git push trac HEAD:u/user_name/branch_name > > > For more details, see http://doc.sagemath.org/html/en/develo

[sage-devel] Re: Git push issues

Hi, Le mardi 6 mars 2018 13:17:56 UTC+1, Meghana.M Reddy a écrit : > > ! [remote rejected] HEAD -> t/24909/boruvka_algorithm_for_mst (hook > declined) > error: failed to push some refs to 'g...@trac.sagemath.org:sage.git' > > The target on trac does not seem correct; the syntax of the push

[sage-devel] Re: Asking for advice: differential operators in the global namespace

Thank you all for your answers! The conclusion is pretty clear: the differential operators will *not* be added to the global namespace at start, even less be added silently when a pseudo-Riemannian manifold is constructed. The only way to get them will be an explicit demand from the user, in

Re: [sage-devel] Re: Asking for advice: differential operators in the global namespace

Hi Vincent, Le dimanche 4 mars 2018 11:35:04 UTC+1, vdelecroix a écrit : > > Hi Eric, > > I agree with Kwankyu and Simon: > - the global namespace is already bloated > - abbreviations should be avoided in most places in Sage > > Thanks for your feedback. > And having the namespace modified

[sage-devel] Re: Asking for advice: differential operators in the global namespace

Hi Simon, Le dimanche 4 mars 2018 08:25:09 UTC+1, Simon King a écrit : > > > > What's wrong with v.div(), to cope with standard notation in SageMath? > > Nothing from my point of view: I also prefer object-oriented notations over functional ones and v.div() is already implemented in the ticket

[sage-devel] Re: Asking for advice: differential operators in the global namespace

> > An alternative (disapproved by the reviewer) is to inject these names in >> the global namespace only if any pseudo-Riemannian manifold is constructed, >> by means of the function sage.repl.user_globals.set_global in >> PseudoRiemannianManifold.__init__, see line 398 of >> this source

[sage-devel] Asking for advice: differential operators in the global namespace

Hi, In Trac #24622 , the standard differential operators gradient, divergence, curl, Laplacian and d'Alembertian are introduced on pseudo-Riemannian manifolds. A demo worksheet is here

Re: [sage-devel] Re: trac logo change ?

Thank you Frédéric and Erik for the new logo shining at the top of Trac pages! Eric. -- 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 issues

Another (probably related) trac issue is that after typing the following command in a linux console: git push trac HEAD: everything seems OK except that one does not get the console prompt back (as if the command has not terminated). Looking at the ticket page, the push seems effective though...

[sage-devel] Re: making database_gap (starting from GAP 4.9) standard - please vote

Le dimanche 18 février 2018 00:01:50 UTC+1, Dima Pasechnik a écrit : > > > Thus I'm calling for a vote on this: to make database_gap standard as soon > as license permits (i.e. as soon as we update to GAP 4.9). > +1 Eric. -- You received this message because you are subscribed to the Google

Re: [sage-devel] "cannot find cimported module 'gmpy2'" when building Sage 8.2.beta5

Le vendredi 16 février 2018 14:22:39 UTC+1, Jeroen Demeyer a écrit : > > > They are warnings, not errors. In this case, you can ignore them since > you probably don't have gmpy2 installed (it is not a standard package). > > Thanks for your answer. If this is not a standard package, why there

[sage-devel] "cannot find cimported module 'gmpy2'" when building Sage 8.2.beta5

Hi, After a successful build of Sage 8.2.beta5 (from a fresh git clone, on Ubuntu 16.04), I'm getting the following messages after each command "./sage -b" or "make" issued from the Sage root directory (see full log attached for details): sage/rings/complex_double.pyx: cannot find cimported

Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

Hi, Le jeudi 15 février 2018 23:59:09 UTC+1, Andy Howell a écrit : > > > I had problems under 17.04. I think I was missing the fortran compiler. > After installing that, it built fine. > > This list of prerequisites to build Sage on Ubuntu is at https://wiki.sagemath.org/prerequisitesUbuntu This

[sage-devel] Re: Live documentation, the return (#24593 needs review)

Hi Nicolas, Thanks for all this! A remark on the demo: Le dimanche 28 janvier 2018 22:42:38 UTC+1, Nicolas M. Thiéry a écrit : > > > To see some live documentation in action: > > > http://sage-package.readthedocs.io/en/latest/sage_package/sphinx-demo.html > > For 3D plots, it is

Re: [sage-devel] Re: color for plot3d axes

Le vendredi 26 janvier 2018 21:19:22 UTC+1, Andy Howell a écrit : > > Eric, > > I tried with threejs. I could not get the labels to show with either sage > 8.0 or sage 8.2beta3. > The labels are here, but they are not placed along the blue arrows of the S object: they are located on other

[sage-devel] Re: color for plot3d axes

Hi, Le mardi 23 janvier 2018 21:58:35 UTC+1, Andy Howell a écrit : > > I was trying to plot a 3d object and was not sure which axes were which > in the plot. > Just for this purpose (i.e. finding which axes are which), note that you can use the threejs viewer, which automatically labels the

[sage-devel] Re: Sage Days next July in Zaragoza (Spain)

Hi Miguel, Le mardi 16 janvier 2018 13:33:58 UTC+1, Eric Gourgoulhon a écrit : > > > For the course "sage development workflow (Trac, git, doctests...)", I > would say 1 h (course) + 1 h (practice). Also it would be good if this can > take place at the b

[sage-devel] Re: Sage Days next July in Zaragoza (Spain)

Hi Miguel, Le mardi 16 janvier 2018 12:40:19 UTC+1, mmarco a écrit : > > In order to organize the schedule, I would like to know how many hours do > you plan to spend in the miny course that you will give. If possible, > separate them in theoretical explanations and practical lessons (or maybe

[sage-devel] Re: Bug report: Could not import nbconvert: No module named base

Le lundi 15 janvier 2018 03:13:53 UTC+1, Victor Porton a écrit : > > > http://localhost:/nbconvert/script/home/porton/math/namespaces/Comparison%20of%20counter-example%20algorithms.ipynb?download=true > > 500 : Internal Server Error > The error was: > > Could not import nbconvert: No module

[sage-devel] Re: typesetting of math formulas in (certain) docstrings is broken

Hi Steven, Le lundi 8 janvier 2018 06:52:41 UTC+1, Steven Trogdon a écrit : > > In the html docs, the `(0,1)` now appears literally as \((0,1)\), i.e. no > math typesetting. > I don't see the issue: (0,1) in this warning appears LaTeX-typeset in the 8.1. documentation posted at

[sage-devel] Re: nbconvert broken in Jupyter notebooks of Sage 8.2.beta*

Since I've got the same issue on a different computer (still running Ubuntu 16.04 though), I've opened a ticket: #24484 . -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

[sage-devel] nbconvert broken in Jupyter notebooks of Sage 8.2.beta*

Hi, After the upgrade to Jupyter 5.2.1 in Sage 8.2.beta0 (cf. #24168 ), the export of a notebook to another format seems broken. For instance, clicking on File -> Download as -> PDF via LaTeX leads to 500 : Internal Server Error The error was: Could

Re: [sage-devel] Re: 8.2.beta0 Doctest error on tensorfield.py

Le lundi 18 décembre 2017 19:01:48 UTC+1, vdelecroix a écrit : > > This is fixed in > > https://trac.sagemath.org/ticket/24396 > > Thank you Vincent! And Eric you should be in copy of that ticket > > No, I wasn't: for some reason, I did not receive any notification from Trac for this

[sage-devel] Re: 8.2.beta0 Doctest error on tensorfield.py

Hi Simon, Le lundi 18 décembre 2017 18:37:14 UTC+1, Simon King a écrit : > > Hi Eric, > > On 2017-12-18, Eric Gourgoulhon <egourg...@gmail.com > > wrote: > > Le lundi 18 décembre 2017 15:58:30 UTC+1, Vincent Klein a écrit : > > I don't know what is the

[sage-devel] Re: 8.2.beta0 Doctest error on tensorfield.py

Hi, Le lundi 18 décembre 2017 15:58:30 UTC+1, Vincent Klein a écrit : > > Hi all, > > I get the following errors with a fresh 8.2.beta0 install (after "make > distclean" "make"). > I have the sames errors on Ubuntu 14.04 and 16.04. > Traceback: > > sage -t --warn-long 17.5

[sage-devel] Re: solve and conjugate bug

This is probably related to the following: sage: var('z') z sage: (z - 4*z.conjugate()).simplify() -3*z which is a bug, given that the documentation of var says: By default, var returns a complex variable Eric. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: manifolds.utilities.py: ExpressionNice()

Hi, Le dimanche 19 novembre 2017 18:27:09 UTC+1, Richard_L a écrit : > > I have found the list of options in manifold.py, and thus in the > documentation under Topological Manifolds. Thank you again. > It is unclear why the documentation search function does not find it, but, > no matter,

[sage-devel] Re: manifolds.utilities.py: ExpressionNice()

HI, Le samedi 18 novembre 2017 23:55:35 UTC+1, Richard_L a écrit : > > Applying ExpressionNice() to an expression containing partial derivatives > cleans up the presentation, suppressing the display of function arguments > in the partial derivatives. However, zeroth order derivatives (i.e., the

<    1   2   3   4   5   6   7   >