[sage-devel] Re: Make OpenBLAS Error

Hi, Just to complete Steven's answer: with Ubuntu 16.04, if you install the Ubuntu package gfortran-5, your Sage build will use the system gfortran, which works fine (no missing libgfortran.so.3). In this case, you do not need the fix introduced in https://trac.sagemath.org/ticket/21689 Best

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

Le mardi 11 octobre 2016 09:51:35 UTC+2, Jeroen Demeyer a écrit : > > > It's annoying that only the patchbots have these errors, I have not seen > anybody else report them. > > A similar build error regarding fermat (sage/matrix/matrix0.pyx:4757:10: '_add_' already defined) is here:

[sage-devel] Build issues with patchbots hades, poseidon and fermat

Hi, Since Sage 7.4.rc0, the patchbots hades and poseidon fail with the message: [openblas-0.2.19] ./openblas_utest: error while loading shared libraries: libgfortran.so.3: cannot open shared object file: No such file or directory while fermat fails with the message: [sagelib-7.4.rc0]

Re: [sage-devel] patchbot Internal Server Error

Le vendredi 7 octobre 2016 13:29:55 UTC+2, Thierry (sage-googlesucks@xxx) a écrit : > > Hi, > > the log acknowledged an error, but it was very unclear, i relaunched the > services and it seems to work now. > > Thank you Thierry! Eric. -- You received this message because you are

[sage-devel] patchbot Internal Server Error

Hi, Since yesterday, whenever I try to read some patchbot report about a ticket, I'm getting the message Internal Server Error from https://patchbot.sagemath.org/ Is it only me ? Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

Hi, I confirm that the new package sagemath-upstream-binary-full, taken from the PPA aims/sagemath-dev works well: SageManifolds could be installed in it without any trouble and its test suite is passed. Thanks a lot Jan ! Best regards, Eric. -- You received this message because you are

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

Hi Jan, Thanks for your prompt and detailed answer, and for your efforts in offering this PPA to the community. Best regards, Eric. Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald a écrit : > > Hi > > On 23 September 2016 at 15:46, Jan Groenewald > wrote: > >>

[sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

PS (to aishen): while this problem is fixed, you may consider installing in your home directory SageMath 7.3 from the file sage-7.3-Ubuntu_16.04-x86_64.tar.bz2 downloaded from http://www.sagemath.org/download-linux.html. Installing SageManifolds in such a version has been tested successfully.

[sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

OK I could reproduce the error, with the following set-up: - Ubuntu 16.04 x86_64 - SageMath 7.3 from AIMS PPA installed as follows: sudo -E apt-add-repository -y ppa:aims/sagemath sudo -E apt-get update sudo -E apt-get install sagemath-upstream-binary-full - SageManifold 0.9.1

[sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

Hi, Le vendredi 23 septembre 2016 11:40:01 UTC+2, aishen a écrit : > > > It was left in the file named: > '/home/pi/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt' > If you can email this file to the developers, the information in it will > help > them in understanding and correcting

[sage-devel] Re: Sage's references: new policy?

Hi John, Le mercredi 21 septembre 2016 01:03:27 UTC+2, John H Palmieri a écrit : > > As discussed in another thread [1]_ on sage-devel recently, I propose > changing our policy toward references: > > - all references should be put into a master bibliography file, and > What about the pdf

[sage-devel] SageManifolds 0.9.1 released

Hi, A new stable version of SageManifolds has just been released. Among the novelties are the computation of the Schouten and Cotton tensors of a pseudo-Riemannian metric and the parallelization (via multiprocessing) of the vector field plots. More details in

[sage-devel] Re: 3d graphics error in Jupyter notebook while legacy Sage notebook is OK

Playing around with this, I found that the order of the graphic objects in the sum matters: graph_v + graph_spher generates the error, while graph_spher + graph_v works fine. Besides, the tachyon viewer works fine in both cases. Only the default 3D viewer (jsmol) yields the error for graph_v +

[sage-devel] 3d graphics error in Jupyter notebook while legacy Sage notebook is OK

Hi, While migrating the legacy Sage notebooks at http://sagemanifolds.obspm.fr/examples.html to Jupyter notebooks (thanks to Volker's notebook exporter introduced in Sage 7.3, cf. #19877 ), I got the error error: Error -3 while decompressing: invalid

[sage-devel] Re: The Sage Wiki

Hi, Thanks for the update of the wiki front page. I've added links to two recent wiki pages resulting from SD74: - On development models for sharing (experimental) code (in the section "Special Discussion Pages") - K3D-jupyter 3D visualisation in

Re: [sage-devel] Re: ExpressionNice

Le vendredi 19 août 2016 20:24:24 UTC+2, Nils Bruin a écrit : > > > Personally, I'm comfortable with the basic representation choices made in > https://trac.sagemath.org/ticket/21286 . > Thanks for this ticket. > I'd be hesitant to go any further. Using leibnitz notation in general >

[sage-devel] Re: ExpressionNice

Hi, Le jeudi 18 août 2016 07:59:15 UTC+2, Nils Bruin a écrit : > > > The situation for topological manifolds is slightly different, because > expressions there live in the context of a chart, where a specific > correspondence between variable name and parameter position has been > imposed.

[sage-devel] Issue with coverage plugin?

Hi, In https://patchbot.sagemath.org/ticket/18843/ the coverage plugin (running on the patchbot ark) failed with the message Traceback (most recent call last): File "/home/ralf/.local/lib/python3.4/site-packages/sage_patchbot/patchbot.py", line 1060, in test_a_ticket baseline=baseline,

Re: [sage-devel] Re: patchbot.sagemath.org down?

Hi, For the record, I also could not reach patchbot.sagemath.org this morning with Firefox 48.0 (under Ubuntu 16.04.1), with an error saying something like "this page cannot be displayed by Firefox because it has some security issue..." Now, it is OK. Thanks for having the pathbot back!

[sage-devel] Re: patchbot.sagemath.org down?

rac tickets. Best wishes, Eric. > Frédéric > > Le dimanche 14 août 2016 18:17:12 UTC+2, Eric Gourgoulhon a écrit : >> >> Hi, >> >> Since yesterday (at least), it seems that patchbot.sagemath.org is >> unreachable. >> >> Eric. >> >>

[sage-devel] patchbot.sagemath.org down?

Hi, Since yesterday (at least), it seems that patchbot.sagemath.org is unreachable. 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: Parent structure class hierarchy

Hi Joseph, For what it's forth, I may tell what is done in SageManifolds (metaticket #18528 ): SageManifolds involves many parent classes. All of them are implemented as direct subclasses of Parent. Their algebraic structures (group, free module,

Re: [sage-devel] Doc does not compile before jmol package

Le mercredi 13 juillet 2016 20:12:46 UTC+2, John H Palmieri a écrit : > > I created https://trac.sagemath.org/ticket/21014 for this. > Thank you John! Best regards, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Doc does not compile before jmol package

Le mardi 12 juillet 2016 15:51:19 UTC+2, Travis Scrimshaw a écrit : > > I'm starting to wonder if there is a dependency (i.e., jmol) of the > docbuilding that isn't yet marked as such. > Yes, it seems that some of us already faced this issue:

[sage-devel] Manual de cálculo científico en SageMath

Hi, I just noticed this reference, which might be useful to Spanish-speaking users: http://oaq.epn.edu.ec/index.php/publicaciones/publicaciones-varios/160-calculo-cientifico-en-sagemath-con-enfasis-en-sagemanifolds Maybe worth to add to http://www.sagemath.org/library-publications.html#books

Re: [sage-devel] Re: patchbot arando

Le mercredi 29 juin 2016 11:33:53 UTC+2, Jeroen Demeyer a écrit : > > > I'm on holidays now, I just stopped the bot. > > Thanks! Sorry for having disturbed you during holidays... Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel"

[sage-devel] patchbot arando

Hi, The patchbot arando is failing with the message File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close raise ResponseError() ResponseError: ResponseError() See for instance https://patchbot.sagemath.org/log/18843/Ubuntu/14.04/i686/3.13.0-86-generic/arando/2016-06-29%2000:09:58

[sage-devel] Re: trac slow/unresponsive

It's OK for me (from Paris). Do you still have any issue? 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

Re: [sage-devel] sage infrastructure at UW

Le lundi 6 juin 2016 19:08:44 UTC+2, Thierry (sage-googlesucks@xxx) a écrit : > > Hi, > > the wiki is back online at University Paris North : > http://sagewiki.lipn.univ-paris13.fr/ > > Thank you very much Thierry! I've checked it on recently modified pages: the Sage Days 74 ones. Everything

[sage-devel] Re: sagemanifolds error

Hi, Le samedi 21 mai 2016 16:30:14 UTC+2, aishen a écrit : > > Hi, > I am on ubuntu 16.10 (16.04 +1), and I can't compile sage 7.2 (flint error) > Si I install ppa version 7.1 and > sudo bash sm-install.sh everythink went well. Typing this in a console or in > sage -n=jupyter get the following

[sage-devel] Program of Sage Days 74

Hi, The program of Sage Days 74 is now online at https://wiki.sagemath.org/days74 For interested people, it's still possible to register. Note also that we are investigating the possibility to have remote participants. By the way, any advice in this matter is welcome (technical solution,

[sage-devel] Re: I added 3d axes labels and wanted to ask some questions before issuing a pull request.

It will be great to have axes labels on 3d plots ! Good luck for your ticket ! 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: sage vs jupyter notebooks

Hi Vincent, I would add to your list: * when exporting to pdf, the LaTeX format of the output cells is lost (cf. https://groups.google.com/d/msg/sage-support/Pt_r9Ct-31w/MWkRz1DVBwAJ) * the menu of JSMol 3D plots is not accessible Best wishes, Eric. -- You received this message because

[sage-devel] Re: On development workflows for sharing (experimental) code

Le vendredi 6 mai 2016 14:38:10 UTC+2, Nicolas M. Thiéry a écrit : > > On Wed, May 04, 2016 at 05:56:36AM -0700, Eric Gourgoulhon wrote: > >Thank you Nicolas for this page which is very instructive. > > :-) > > >I've added some comments on SageManifolds work

[sage-devel] Re: On development workflows for sharing (experimental) code

Thank you Nicolas for this page which is very instructive. I've added some comments on SageManifolds workflow. 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

[sage-devel] Re: disk space

Hi, Building Sage 7.2.beta4 from source after a fresh git clone results in a sage root directory of 5.9 GB on Ubuntu 15.10. Best regards, Eric. Le jeudi 21 avril 2016 03:09:23 UTC+2, William a écrit : > > Hi, > > How much disk space is it supposed to take to download and build Sage >

Re: [sage-devel] Coming SageMathCell upgrade - please test!

Hi, Le lundi 18 avril 2016 10:58:48 UTC+2, Thierry (sage-googlesucks@xxx) a écrit : > > Hi, > > it works almost well on iceweasel (Firefox 38.7.1) on Debian jessie > (stable). I see however two issues. > > First, autocompletion does not work, when i click on , the cursor > jumps on

[sage-devel] Re: Calculus bug in the latest 7.2.beta: sin(pi*x) returns 0 whenever x > 0

Thanks ! 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] Calculus bug in the latest 7.2.beta: sin(pi*x) returns 0 whenever x > 0

Hi, In Sage 7.2.beta4: sage: assume(x>0) sage: sin(pi*x) 0 As far as I can tell, this bug has been introduced in Sage 7.2.beta0. Maybe by ticket #20134 (upgrade to pynac-0.6.4) ? Best wishes, Eric. -- You received this message because you are

[sage-devel] Re: online documentation and "long time"

Le mardi 22 mars 2016 10:38:43 UTC+1, Harald Schilly a écrit : > > > > On Tuesday, March 22, 2016 at 9:49:29 AM UTC+1, Samuel Lelievre wrote: >> >> >> Shouldn't the "long time" stuff appear anyway in the online >> documentation? >> > > Well, do you have any idea how to do that? > > It's easy:

[sage-devel] Re: documentation changed in 7.1?

Hi, Le lundi 21 mars 2016 14:26:40 UTC+1, Harald Schilly a écrit : > > Well, never mind. I think it still works and I see that there are more > plots. Would have been nice to have a heads up about this … > > Apart from the location of the doc output, now in local/share/doc/sage/html (instead of

[sage-devel] Re: LaTeX names of symbolic functions lost after simplification

Thanks for these detailed explanations. I understand that the fix requires some significant work on symbolic functions. This would be quite nice however, since most symbolic computations require simplification at the end. In the current setting, the LaTeX symbol is thus always lost. --

[sage-devel] LaTeX names of symbolic functions lost after simplification

Hi, It seems that simplifying an expression containing a symbolic function causes the loss of the LaTeX name of the latter: sage: s = function('g', latex_name=r'\Gamma')(x) sage: s g(x) sage: latex(s) \Gamma\left(x\right) sage: latex(s.simplify()) g\left(x\right) sage: latex(s.simplify_full())

Re: [sage-devel] Reproducability of results

Hi, Le mardi 23 février 2016 16:39:20 UTC+1, William a écrit : > > > It seems to me that > > sage: x = var('x') > sage: bool(x!=infinity) > False > > *is* a newly introduced bug. I can't understand how the above > behavior could be justified > In the same vein, note that sage: x =

Re: [sage-devel] Re: cannot post comments on trac #19984

Hi, Just to tell that I also have exactly the same problem from time to time (last time, a few days ago). Sometimes, changing the browser (from Firefox to Chromium) helps, sometimes not... Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Random doctest error in real_double.pyx

This is now http://trac.sagemath.org/ticket/19962 Le lundi 25 janvier 2016 15:19:31 UTC+1, Volker Braun a écrit : > > I've seen random test error there, too. +1 to removing them. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] Re: Hm, seemingly wrong bracketing works anyway?

Quite surprising! Indeed, one has sage: preparse("[1..len(a])") '(ellipsis_range(Integer(1),Ellipsis,len(a)))' So the culprit seems to be sage preparser. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Random doctest error in real_double.pyx

Hi, It appears that occasionaly the following doctest error occurs in src/sage/rings/real_double.pyx: File "src/sage/rings/real_double.pyx", line 2789, in sage.rings.real_double.time_alloc Failed example: pool_stats() Expected: Used pool 0 / 0 times Pool contains 7 / 50 items Got:

Re: [sage-devel] Plots in plot.py documentation

+1 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] plugins.startup_modules error

Hi, On the ticket http://trac.sagemath.org/ticket/18529 the patchbots report a failed plugins.startup_modules: http://patchbot.sagemath.org/ticket/18529/ Clicking on "diff", one gets the report == plugins.startup_modules == --- 7.0.beta3 +++ 7.0.beta3 + #18529 -Total count:

[sage-devel] Re: plugins.startup_modules error

Le lundi 11 janvier 2016 12:38:50 UTC+1, Volker Braun a écrit : > > Its not really an error, but one should strive to not add unneccessary > modules. > > > Yes, I thought this was taken into account by using only lazy_import, as we do (except in sage.all, where the import from

Re: [sage-devel] plugins.startup_modules error

Le lundi 11 janvier 2016 12:35:36 UTC+1, vdelecroix a écrit : > > Hello Eric, > > The plugin is very naive: it just looks for new modules on startup. And > you added one. You should not worry about it. The patchbot green light > is not at all mandatory to get a ticket reviewed. > > OK, I

[sage-devel] Re: patchbot hera-optiplex

Hi, I confirm that the patchbot hera-OptiPlex-7010 misbehaves: it systematically returns "build failed" with the message The content of "/home/hera/sage-patchbot/build/pkgs/r_jupyter/type" must be 'base', 'standard', 'optional', 'experimental' or 'pip' Apply -- 4 seconds Traceback (most recent

[sage-devel] Re: Sage 6.10.rc2 binaries test

Hi, I've tested sage-6.10.rc2-Ubuntu_15.10-x86_64.tar on a Ubuntu 15.10 computer and got the following issue: ./sage -n jupyter results in the error message: Please wait while the Sage Notebook server starts... [I 11:01:15.391 NotebookApp] Using MathJax: nbextensions/mathjax/MathJax.js [W

Re: [sage-devel] Re: Build failure on Debian testing

Le vendredi 18 décembre 2015 01:19:17 UTC+1, Dima Pasechnik a écrit : > > > yeah, your compiler is too new... (I don't think we got Sage to build with > gcc 5; > Yes we got: Sage 6.10.rc2 compiles like a charm with gcc 5.2.1 under Ubuntu 15.10. Best wishes, Eric. -- You received this

[sage-devel] Re: [sage-release] Re: Sage-6.10.rc1 binaries test

Hi, Le jeudi 17 décembre 2015 18:10:43 UTC+1, kcrisman a écrit : > > > I'd +1 that; I haven't tested these binaries yet since I don't have El > Capitan but I agree that is not very user-friendly. > Note that this issue is not specific to OS X: the long patching takes place with Linux as well

[sage-devel] Re: [sage-release] Re: Sage-6.10.rc1 binaries test

Le jeudi 17 décembre 2015 20:30:52 UTC+1, Volker Braun a écrit : > > The patching can be done faster, but it has to work first ;-) Also I'm > pretty sure that it even now is much faster than the unpacking of the > tarball. In any case I've added a message. > > > Thanks. I think that with a

[sage-devel] Re: Sage 6.10.rc2 binaries test

I've tested sage-6.10.rc2-Ubuntu_14.04-x86_64.tar.bz2. Looks good to me (the Jupyter issues are fixed). Thanks. -- 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: Sage-6.10.rc1 binaries test

Hi, I've tried sage-6.10.rc1-Ubuntu_14.04-x86_64.tar.bz2 on a x86-64 laptop with Ubuntu 14.04. I've noticed some issues: 1/ The patching at first run took ages (12 min on Intel Core i5-2410 M with 4 GB RAM) (maybe one should warn the user about this, since he might expect a binary to run

[sage-devel] Re: Sage-6.10.rc1 binaries test

Hi, Le mardi 15 décembre 2015 10:41:49 UTC+1, Eric Gourgoulhon a écrit : > > > 2/ The Jupyter notebook opened with ./sage -n jupyter starts with an > error message > > Failed to retrieve MathJax from '/nbextensions/mathjax/MathJax.js' > > Math/LaTeX rendering will be

Re: [sage-devel] bug report using assume

Hi Vincent, Le mardi 15 décembre 2015 23:17:26 UTC+1, Thierry (sage-googlesucks@xxx) a écrit : > > > I can reproduce this on 6.10.rc1, Debian jessie x86_64. > > I can reproduce it as well. This seems linked to the ternary logic introduced in Sage 6.10.beta7 (cf. a similar issue reported in

[sage-devel] Re: Sage-6.10.rc1 binaries test

while it should be SAGE_ROOT/local/share/jsmol Le mardi 15 décembre 2015 21:35:12 UTC+1, Eric Gourgoulhon a écrit : > > Hi, > > Le mardi 15 décembre 2015 10:41:49 UTC+1, Eric Gourgoulhon a écrit : >> >> >> 2/ The Jupyter notebook opened with ./sage -n jupyter st

[sage-devel] Re: Sage Days 74: differential geometry and topology, Paris, 30 May - 2 June 2016

Le lundi 14 décembre 2015 12:11:02 UTC+1, mmarco a écrit : > > Damn. I would love to attend, but i have teaching duties that week. > Sorry but there is little flexibily about the dates at this stage. > > Is it supposed to deal only with differential topology or also other kinds > of

[sage-devel] Sage Days 74: differential geometry and topology, Paris, 30 May - 2 June 2016

to contact the organizers to propose one. The organizing team: Eric Gourgoulhon Marco Mancini Travis Scrimshaw -- 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] SageManifolds 0.9 released

Hi, The version 0.9 of SageManifolds has just been released at http://sagemanifolds.obspm.fr/ As mentioned in this previous post , this release is based on the reorganization of the code for its submission to Sage, through

[sage-devel] Change of logic regarding symbolic expressions in Sage 6.10.beta7

Hi, In Sage 6.10.beta7: sage: bool(x == 0) False sage: bool(x != 0) True sage: x = SR.var('x', domain='real') sage: bool(x == 0) False sage: bool(x != 0) False The latest output differs from what one would get from Sage 6.10.beta6 (and any previous version of Sage), which would have been True,

[sage-devel] Re: Do we really need Element, RingElement, AdditiveGroupElement, ...?

Hi, Le lundi 23 novembre 2015 10:55:40 UTC+1, Jeroen Demeyer a écrit : > > Of course, you could argue that Element > should not have __add__ and __mul__ (since not all elements can be added > or multiplied). But it doesn't really hurt to have them and raise > NotImplementedError (unless I'm

Re: [sage-devel] Re: Do we really need Element, RingElement, AdditiveGroupElement, ...?

Thanks Jeroen and David for your answer and explanations. It's true that OOP with deep hierarchy is not the only possible approach. For instance, there is also the paradigm of component aggregation, see e.g. http://cowboyprogramming.com/2007/01/05/evolve-your-heirachy/ Maybe the latter is closer

Re: [sage-devel] Re: Manifold equality and UniqueRepresentation

Hi, Le dimanche 8 novembre 2015 07:32:48 UTC+1, David Roe a écrit : > > > > I think Nils' point about the downsides of having a cache is one reason > not to use UniqueRepresentation, both because it can generate references to > objects you might want to forget, and because sometimes you just

[sage-devel] Re: Manifold equality and UniqueRepresentation

Hi, Le vendredi 6 novembre 2015 00:16:26 UTC+1, Nils Bruin a écrit : > > On Thursday, November 5, 2015 at 2:35:57 PM UTC-8, Eric Gourgoulhon wrote: >> >> Yes charts are immutable: a chart is defined by two parameters, which are >> passed to the constructor: its dom

Re: [sage-devel] bug in interreduced_basis

I confirm the crash on Ubuntu 14.04, 64-bits, with Sage 6.9, as well as with Sage 6.10.beta1, both compiled from source: Attaching gdb to process id 2853. Saved trace to /home/eric/.sage/crash_logs/sage_crash_iapJz_.log

[sage-devel] Re: Manifold equality and UniqueRepresentation

Hi Simon, Thanks for your feedback! Le jeudi 5 novembre 2015 10:17:35 UTC+1, Simon King a écrit : > > Hi Eric, > > > Are you serious? Certainly you are aware that there is no algorithm that > would be able to test whether two arbitrary compact 4-manifolds are > homeomorphic. And if I am not

[sage-devel] Re: Manifold equality and UniqueRepresentation

Le jeudi 5 novembre 2015 10:32:29 UTC+1, Simon King a écrit : > > > - Or IF you really want to use them as dictionary keys, then just let > manifolds compare by identity (so, you allow that two homeomorphic > manifolds evaluate as non-equal), and have a separate method >

[sage-devel] Re: Manifold equality and UniqueRepresentation

Le jeudi 5 novembre 2015 01:57:27 UTC+1, Nils Bruin a écrit : > > On Wednesday, November 4, 2015 at 2:10:51 PM UTC-8, Eric Gourgoulhon wrote: >> >> Hi sage-dev, >> >> There is an ongoing discussion at #18529 >> <http://trac.sagemath.org/ticket/18529&g

[sage-devel] Re: Manifold equality and UniqueRepresentation

For the benefit of the discussion, here is the list of dictionaries involved in the manifold tickets colllected at #18528 . Each dictionary is presented in the form - values | key: the key - chart restrictions | key: open subset (i.e. manifold) -

[sage-devel] Re: Manifold equality and UniqueRepresentation

Thanks for your suggestions. Le jeudi 5 novembre 2015 18:54:40 UTC+1, Nils Bruin a écrit : > > On Thursday, November 5, 2015 at 7:22:10 AM UTC-8, Travis Scrimshaw wrote: >> >>So I'm somewhat inclined to use EqualityById and let the pickling be >> broken (and redefining _test_pickling to do

[sage-devel] Manifold equality and UniqueRepresentation

Hi sage-dev, There is an ongoing discussion at #18529 about defining __eq__ for manifolds and whether one should use UniqueRepresentation (which implements equality by id). If anybody has any opinion on this, she/he is welcome to join the discussion.

[sage-devel] Re: source code comments: doctesting instructions

Le jeudi 29 octobre 2015 13:23:56 UTC+1, Samuel Lelievre a écrit : > > > - # not tested > + # doctest: skip > > - # not tested (random order) > + # doctest: skip (random order) > > - # optional - qepcad > + # doctest: optional - qepcad > > +1 Eric. -- You received

[sage-devel] Re: source code comments: doctesting instructions

+1 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

Re: [sage-devel] Spurious error report from patchbot plugin doctest_continuation

Thanks Vincent for your reply. I've reported the issue to the patchbot github page. Eric. PS: I agree that starting a line by "..." is not very orthodox typography but it is commonly used to stress that the sentence is the continuation of a preceeding statement, isn't it? -- You received

[sage-devel] Spurious error report from patchbot plugin doctest_continuation

Hi, On the ticket http://trac.sagemath.org/ticket/18529 the patchbots report a failed plugins.doctest_continuation: http://patchbot.sagemath.org/log/18529/Gentoo%20Base%20System/2.2/x86_64/3.2.1-gentoo-r2/sage4/2015-10-20%2023:53:22?plugin=plugins.doctest_continuation This is caused by line 779

[sage-devel] Re: Manifold tickets ready for review

Le vendredi 16 octobre 2015 00:54:04 UTC+2, Eric Gourgoulhon a écrit : > > > All the objects are implemented within Sage's category framework, following > the parent/element scheme. The category for manifolds is Sets() for the > moment, but this should be changed to Manifolds() as

[sage-devel] Manifold tickets ready for review

Dear Sage devs, SageManifolds has been split in various tickets for submission to Sage. They are now ready for review at http://trac.sagemath.org/ticket/18528 This split has been the opportunity to reorganize many things in the project, among which: - the

Re: [sage-devel] Re: Parallel computing

Hi, Le lundi 5 octobre 2015 07:36:05 UTC+2, William a écrit : > > Type > >parallel? > > in Sage for a simple but very useful parallel decorator in Sage, that > I addedabout 6 years. The API is slightly confusing, and it would be > nice to have something better. But it's pretty easy to

Re: [sage-devel] Re: Docs: Symbols and `self`

Le lundi 28 septembre 2015 08:46:12 UTC+2, Jori Mäntysalo a écrit : > > On Fri, 25 Sep 2015, Travis Scrimshaw wrote: > > >>> 2) What about `self` in docstrings? > > >> There was a discussion about this some time ago: > >> https://groups.google.com/d/msg/sage-devel/58RUzV32vI0/rf4Mldr60JkJ >

Re: [sage-devel] Sources of funding - perhaps computer manufacturers?

Le dimanche 27 septembre 2015 20:20:18 UTC+2, William a écrit : > > > > On Sunday, September 27, 2015, Nathann Cohen > wrote: > >> What about the >> manifold guys, for instance? Are they joining the project or do they >> still develop on their own? >> >> > I think

[sage-devel] Re: Docs: Symbols and `self`

Hi, Le vendredi 25 septembre 2015 08:45:34 UTC+2, Jori Mäntysalo a écrit : > > More on docstrings: > > "The Frattini sublattice `\Phi(L)` is the intersection - -" vs. "Returns > the Frattini subgroup of ``self``. The Frattini - -". > > 1) Should we include symbols in docstrings? I.e. add

Re: [sage-devel] Re: Docs: Symbols and `self`

Le vendredi 25 septembre 2015 16:47:23 UTC+2, William a écrit : > > > > we may assume that most users understand LaTeX. > > This is a questionable assumption. Numerical most users of Sage are > undergraduates, and most undergraduates don't know about LaTeX. > > Yes you are right! The

[sage-devel] Re: Help SageMath-Android

Hi, Le lundi 21 septembre 2015 21:45:28 UTC+2, Andrey Novoseltsev a écrit : > > Can someone with an Android system take a look at this? Is it device > specific or the same strange thing happens for everybody? > It works fine for me: - Galaxy SIII mini with Android 4.1.2 - version() returns

Re: [sage-devel] Re: SageManifolds Install Issue

Hi Jan, Le jeudi 10 septembre 2015 11:28:12 UTC+2, Jan Groenewald a écrit : > > Hi Eric, > > You might want to disable the dev PPA. Within a week or two we will copy a > sage 6.8 to the stable PPA. The dev PPA will get automated uploads as we do > testing (probably weekly): > > sudo mv

[sage-devel] Re: Cannot start sage notebook with Ipython interface

Hi, Le jeudi 10 septembre 2015 21:38:54 UTC+2, Volker Braun a écrit : > > You need the system-wide ssl development package, e.g. openssl-devel on > redhat. Then recompile all of sage (make distclean && make) > > On Ubuntu, the openssl development package is called libssl-dev. Eric. -- You

Re: [sage-devel] Re: SageManifolds Install Issue

Hi Jonathan, Le mercredi 9 septembre 2015 16:49:06 UTC+2, Jonathan Carter a écrit : > > This is all fixed now in the ~aimsppa12 version, so doing and apt-get > update and installing the new version should also do the trick. > > > Thanks! It works now. I could install the package

Re: [sage-devel] Re: SageManifolds Install Issue

Hi Jan, Thank you for having prepared a Ubuntu package with the sources included! I've tried to install it but the step sudo apt-get install sagemath-upstream-binary-full results in the following error: Décompactage de sagemath-upstream-binary-full (6.8~aimsppa11) ... dpkg: error processing

Re: [sage-devel] Re: SageManifolds Install Issue

Hi Thierry, Le mardi 8 septembre 2015 17:55:50 UTC+2, Thierry (sage-googlesucks@xxx) a écrit : > > > cd /opt/sagemath/sage > wget http://sagemanifolds.obspm.fr/spkg/sm-install.sh > chmod +x sm-install.sh > ./sm-install.sh > keep dir /opt/sagemath > > Thank you for these

Re: [sage-devel] Re: UniqueRepresentation: class vs. class_with_category

Hi, I would endow the parent class C with a method new_instance(), as in the following example: sage: class C(Parent, UniqueRepresentation): : def __init__(self, data, category=Sets()): : Parent.__init__(self, category=category) : self._data = data : def

[sage-devel] Re: Short fr, de, pt, ru translation

Pour des fonctionnalités GAP, vous devez installer deux paquetages Sage optionnels. Cela peut être fait avec la commande:: (A question to French colleagues: maybe Pour des fonctionnalités GAP should be replaced by Pour utiliser GAP or something else...) -- You received this message because you

[sage-devel] Re: Pictures in documentation

Hi, Le mardi 21 juillet 2015 11:40:10 UTC+2, Jori Mäntysalo a écrit : http://trac.sagemath.org/ticket/18932 This is first example of ..PLOT used (if not counting what Nathann made when he implemented this feature). Another example is the documentation of the functions plot() of

[sage-devel] Re: Announcing $0M in new funding for the SageMathCloud over the next 3 years

Hi, Le mercredi 8 juillet 2015 22:43:36 UTC+2, c.d. mclean a écrit : for the SMC community, if you use this service and can forego the purchase of a bag of coffee beans each month, then i assure you that you ABSOLUTELY WANT to become an SMC customer ... this project is simply too important

[sage-devel] Re: We can now have pictures in our documentation

Hi Nathann, Many thanks for this very useful enhancement! I am using it in #18528 and have noticed that the Sage preparser is not invoked in the series of instructions between .. PLOT:: and sphinx_plot(...): we cannot use the trick and we have to write x**2 instead of x^2. Is there a way to

Re: [sage-devel] Re: We can now have pictures in our documentation

Thanks for your prompt answer. As I said, this is not a big deal, since everything can be reformulated without the Sage preparser. Btw, I have another remark: in the online reference manual on sagemath page, clicking on (Source code) next to a plot results in a 404 error, see e.g. the plot of

<    1   2   3   4   5   6   7   >