[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

[sage-devel] Re: Pattern matching in Sage

Le dimanche 12 novembre 2017 16:04:38 UTC+1, Eric Gourgoulhon a écrit : > > > Yes for sure, I will rewrite it using the expression tree walker, but in > another ticket. > This is now #24232 <https://trac.sagemath.org/ticket/24232>. This ticket rebases all simpli

Re: [sage-devel] Python3 and super()

Thanks Jeroen for your answer. Accordingly, I am keeping the Python-2 way. Best regards, 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: Python3 and super()

Le jeudi 16 novembre 2017 15:02:36 UTC+1, Eric Gourgoulhon a écrit : > > so this should hamper the transition to Python3 > Yet another typo: "this should hamper" --> "this should not hamper" Sorry. -- You received this message because you are subscribed to the G

[sage-devel] Re: Sage (pynac ?) doesn't evaluate some (trivial) identities.

On a similar note, arctan suffers from some lack of simplification: sage: assume(-pi/2

[sage-devel] Re: Sage (pynac ?) doesn't evaluate some (trivial) identities.

Le lundi 13 novembre 2017 08:27:53 UTC+1, Emmanuel Charpentier a écrit : > > > Ticket-worthy ? (I think so...) > > +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

[sage-devel] Re: Pattern matching in Sage

Hi, Le dimanche 12 novembre 2017 14:45:54 UTC+1, Ralf Stephan a écrit : > > Is the documentation really so bad that you couldn't find > > http://doc.sagemath.org/html/en/reference/calculus/sage/symbolic/expression_conversions.html > > Of course Sage uses pattern matching, e.g. to convert

Re: [sage-devel] Re: installation of ipykernel failed (when SAGE_PROFILE=yes)

Le lundi 6 novembre 2017 17:22:56 UTC+1, vdelecroix a écrit : > > > The error message from both the thread and the ticket you mentioned is > different > > Actually, on my computer, I got exactly the same error message as you (cf. the log file attached to

[sage-devel] Re: installation of ipykernel failed (when SAGE_PROFILE=yes)

Hi Vincent, Le lundi 6 novembre 2017 16:48:10 UTC+1, vdelecroix a écrit : > > ImportError: No module named IPython.core.profiledir > Running setup.py install for ipykernel: finished with status 'error' > > > This is the failure discussed on sage-release:

[sage-devel] Segfault in Expression.coefficients involving symbolic functions

Hi, In Sage 8.1.beta8 and all previous versions (at least down to 7.5.1), we have sage: s = function('f')(x) * x^2 sage: s.coefficients(x) # OK [[f(x), 2]] sage: s = diff(function('f')(x), x) * x^2 sage: s.coefficients(x) # Bam! Erreur de segmentation (core dumped) Is this a known bug?

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

Hi, Le mardi 31 octobre 2017 13:01:44 UTC+1, mmarco a écrit : > > > The idea is to cover those aspects of the Sage development workflow that > are not usually covered in tutorials. > This sounds a very good idea! I could possibly take part in these Sage Days and give an introductory course

[sage-devel] Re: Getting rid of the pickle jar

Hi, Le vendredi 27 octobre 2017 10:42:53 UTC+2, Jeroen Demeyer a écrit : > > Since the pickle jar doesn't do what it is meant to do, I suggest to be > pragmatic and remove it completely. > > +1 Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel"

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

Thanks Emmanuel for the discussion summary. Le mardi 24 octobre 2017 20:58:17 UTC+2, Emmanuel Charpentier a écrit : > > > It is true. But we are hoisted by our own petard : from our tutorial > : > "The Sage download file comes with

[sage-devel] Re: broken docbuild in SageMath 8.1.beta9

It seems to me (but I may be wrong) that building the doc requires two runs, like latex: during the first pass, all references are collected and are listed as "undefined" if the anchor has not been encountered yet; it is only during the second run that all references are correctly resolved. It

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

Hi, Having read the discussion, I would add a big +1 to what Thierry proposes in https://groups.google.com/d/msg/sage-devel/fE45025Wphs/FheYtjBWAAAJ So I guess that in terms of vote this means |X| Yes, we should fully support OpenSSL now, and clarify the licensing issue. BUT following

[sage-devel] Re: Using C++ library from Sage

Thank you all for your answers. This is very helpful. 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

[sage-devel] Using C++ library from Sage

Hi Sage Devs, We plan to develop some experimental package for Sage, which requires to make use of a C++ library (basically this is to implement numerical calculus on manifolds). What would you recommend to make the link between Sage (Python) code and that library? - Cython ? - Boost ? -

[sage-devel] Re: Sage running on mybinder!

Fantastic! Thanks for your work on this. Best regards, 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

[sage-devel] Outdated duplicate version of Sage Developer's guide

Hi, I've just come to [1] http://www.sagemath.org/git-developer-guide/ which seems quite outdated with respect to [2] http://doc.sagemath.org/html/en/developer/ Shouldn't [1] be deleted? Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: sage downloads

Hi, Le jeudi 28 septembre 2017 14:58:50 UTC+2, kcrisman a écrit : > > 2) There are a LOT fewer mirrors than just a few months ago, if I read it > right; North America used to have six or seven ... did something change? > Same thing for Europe: there used to be much more mirrors. In particular,

Re: [sage-devel] Re: changelogs missing in http://www.sagemath.org/changelogs/index.html

Le mardi 26 septembre 2017 13:28:44 UTC+2, William a écrit : > > > No files were lost. It's just that every time I make the files available > to Jereon, I'm too busy and he tends to ignore me, and every time he asks > for them from me, I tend to be too busy and ignore him... > > Thanks for this

[sage-devel] Re: changelogs missing in http://www.sagemath.org/changelogs/index.html

Yes it's a pity. A big project like Sage should have a changelog at each new release. My understanding is that 1/ the automated script generating the raw changelog from the git logs was lost somehow (during some migration of server?) 2/ it requires some volunteer to maintain such a file

Re: [sage-devel] _richcmp_ versus __eq__ for scheme points

Le vendredi 8 septembre 2017 11:15:10 UTC+2, Jeroen Demeyer a écrit : > > (I am starting to wonder if I should write a blog post explaining this, > it's not the first time that somebody asks this). > Yes please ! Thank you. Eric. -- You received this message because you are subscribed to

[sage-devel] Re: [sage-support] For info ?

Thank you Jan for having maintained the PPA during all these years! Best regards, 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: python3 in sage

Le vendredi 25 août 2017 19:35:27 UTC+2, Nils Bruin a écrit : > > Something along the lines of > > import sage.repl.ipython_kernel.install > sage.repl.ipython_kernel.install.JUPYTER_PATH = > spec = sage.repl.ipython_kernel.install.SageKernelSpec() > spec.update() > > With any luck, you'll see

[sage-devel] Re: python3 in sage

Hi, Le jeudi 24 août 2017 23:17:07 UTC+2, Nils Bruin a écrit : > > If you're using jupyter for non-sage-specific purposes (apparently relying > on a system python3), why not use system jupyter? Personally, I just > install the sage-jupyter kernel in the system jupyter. > This sounds nice!

Re: [sage-devel] Issues with Fourier series

Le mercredi 9 août 2017 14:53:28 UTC+2, David Joyner a écrit : > > > Thanks for looking into this, Eric. I agree with your comments that the > docs > (and possible the code) needs some improvement. > > OK, thanks. This is now https://trac.sagemath.org/ticket/23672 Eric. -- You received

[sage-devel] Re: sage days 91?

Hi, Le mercredi 16 août 2017 11:33:39 UTC+2, Simon Brandhorst a écrit : > > Dear all, > > Ursula, Tony, and I are organizing a weekend workshop "Open Source > Computation and Algebraic Surfaces" at BIRS > https://www.birs.ca/events/2017/2-day-workshops/17w2677. > Our goal is to get some

Re: [sage-devel] Re: SIGSEGV in Maxima

Le vendredi 11 août 2017 11:22:24 UTC+2, Eric Gourgoulhon a écrit : > > Hi, > > Le vendredi 11 août 2017 08:12:42 UTC+2, David Roe a écrit : >> >> Note that this is changed in https://trac.sagemath.org/ticket/23592 >> > > This is not the same part

Re: [sage-devel] Re: SIGSEGV in Maxima

Le vendredi 11 août 2017 15:30:08 UTC+2, Richard_L a écrit : > > Eric, > I will be happy to test as soon as source code is modified. Just let me > know. > For sure I will. Thanks. Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] Re: SIGSEGV in Maxima

Le vendredi 11 août 2017 16:21:45 UTC+2, Richard_L a écrit : > > That's a bit puzzling. In the Sage code, line 36 defines the manifold over > the real field. That is supposed to be inherited by the chart in line 39: > > M = Manifold(1*3,'R^3',field='real',start_index=1) > U = M.open_subset('U') >

Re: [sage-devel] Re: SIGSEGV in Maxima

Hi, Le vendredi 11 août 2017 08:12:42 UTC+2, David Roe a écrit : > > Note that this is changed in https://trac.sagemath.org/ticket/23592 > This is not the same part of manifolds code: #23592 deals with comparison of points

[sage-devel] Issues with Fourier series

Hi, It seems that the only way to compute with Sage the Fourier series of a periodic real function is through the methods fourier_series_* of piecewise-defined functions . Let us take a trivial example: the

[sage-devel] Re: error accessing np.random?

Le jeudi 3 août 2017 14:18:46 UTC+2, mforets a écrit : > > could someone confirm the error? > I confirm. > is it an error on NumPy's or Sage's side? Thanks. > Maybe on Sage's side: if you run the same thing in a python 2 kernel from sage -n jupyter, you don't get the error. Best

Re: [sage-devel] Re: Would it be a good idea to start working on a module on Population Dynamics?

Hi Travis, Le mardi 25 juillet 2017 08:43:47 UTC+2, Travis Scrimshaw a écrit : > > SageManifolds has now been fully integrated into Sage proper, so it > probably should not be on the list. > I've just removed it ;-) Regards, Eric. -- You received this message because you are subscribed to

Re: [sage-devel] Re: DeprecationWarning: OpenSSL.rand is deprecated (on sage 8.0)

Le mardi 25 juillet 2017 10:26:54 UTC+2, vdelecroix a écrit : > > I think the bug appears when I install pyopenssl. Can somebody else > check whether the following shows the warning? > > $ sage -pip install pyopenssl > $ sage -q > sage: quit > $ > > I confirm. > The above can be reverted

[sage-devel] Re: DeprecationWarning: OpenSSL.rand is deprecated (on sage 8.0)

Hi Vincent, I've installed Sage 8.0 on Ubuntu 16.04 from a fresh git clone and without any optional package (i.e. just performing make after the git clone). I do not get any deprecation warning when quitting. Best regards, Eric. Le lundi 24 juillet 2017 16:05:28 UTC+2, vdelecroix a écrit :

[sage-devel] Re: What to do with the "Timed out" failures of patchbots?

Le dimanche 9 juillet 2017 07:10:37 UTC+2, Ralf Stephan a écrit : > > (5) Test manually not once but 10 times since the long runs may not happen > in 100% of all runs > I did: all 10 standalone doctests of src/sage/graphs/matchpoly.pyx returned "All tests passed" in 3.3 s each. Moreover, the

Re: [sage-devel] What to do with the "Timed out" failures of patchbots?

HI, Le samedi 8 juillet 2017 19:34:16 UTC+2, Kwankyu Lee a écrit : > > I observed another "Timed out" on a patchbot: > > sage -t --long src/sage/graphs/matchpoly.pyx > Timed out > I've just got the same issue on a patchbot run on my computer, launched with the command python -m

[sage-devel] Re: About the patchbot queue

Thanks for your answer. The author is not trusted probably because it is his first ticket in Sage. What is the policy about this? Does an author become trusted after a first ticket by him has been accepted? I understand we are short of patchbots and I am considering setting up one in my

[sage-devel] About the patchbot queue

Hi, I am reviewing the ticket https://trac.sagemath.org/ticket/22951; it has been in the status "needs_review" for 10 days and yet has not been visited by any patchbot. Is such a long queueing delay common? Can something be done to trigger a first patchbot visit? Thanks for your help. Eric.

[sage-devel] Re: About milestone sage-feature

Le dimanche 2 juillet 2017 08:03:36 UTC+2, Kwankyu Lee a écrit : > > To encourage people to contribute their feature branches and keep the code > healthy, I suggest: > > 1. Add a new ticket status "needs_feedback". This is a status between > "new" and "needs_review". > 2. Let patchbots test

Re: [sage-devel] ask.sagemath down?

Thanks for your answer Thierry! -- 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] ask.sagemath down?

Hi, Since this morning, it seems that ask.sagemath.org is not responding... Any idea of what's happening? 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: Jupyter notebook: typeset formulas in pdf-export

Hi, As Jupyter is becoming the default notebook in Sage 8.0, I guess it would be nice to fix this, otherwise many users could be quite disappointed when getting such a bad pdf export of their notebooks. I've opened the ticket https://trac.sagemath.org/ticket/23330 although I've no clue how to

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

+1 (a list can have a single item anyway) -- 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

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

+1 for Daniel's proposal: G4. An OUTPUT block is recommended unless it is clear from the one-line > explanation. If in doubt include it. > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

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

-1 (fully agree with Vincent) -- 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: Poll for issue G2 a specific guideline for writing docstrings

+1, although I agree with Travis that ``self`` is technically precise and unambiguous (but for users not familiar with Python, who would read the inline documentation obtained via the question mark, ``self`` can be disturbing) What is the policy of other Python projects regarding this? --

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

-1 (typesetting adds readability) -- 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: trac unresponsive

Hi, Le mercredi 3 mai 2017 08:32:26 UTC+2, Ralf Stephan a écrit : > > I can ping trac but the main page doesn't come up. > It's OK from here (Paris). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Re: first python3 build of sage

Le mardi 18 avril 2017 21:25:44 UTC+2, Frédéric Chapoton a écrit : > > > I just managed (using tricks to avoid a few remaining issues in > cythonization and packages) to get make succeed in building sage with > SAGE_PYTHON3=yes > Congratulations!!! This is already an impressive achievement!

[sage-devel] Re: SageNB -> Jupyter conversion needs testers

Hi, Le mercredi 12 avril 2017 00:08:34 UTC+2, Dima Pasechnik a écrit : > > the whole process is very stressful at the moment, I think. This popup > with password prompt really should not be there... > +1 Also, what is this command "jupyter notebook list" ? Running ./sage -sh jupyter notebook

Re: [sage-devel] Sage 7.5 for Windows?

Le vendredi 31 mars 2017 10:51:29 UTC+2, Erik Bray a écrit : > > > I would still suggest they use Docker... > > OK, I've answered to the ask.sagemath user accordingly. Please correct my answer if necessary (I am not using Windows myself, nor Docker...). Best regards, Eric. -- You received

Re: [sage-devel] Sage 7.5 for Windows?

Hi, Le samedi 18 mars 2017 14:27:49 UTC+1, Volker Braun a écrit : > > Yes, its scripted ( > https://bitbucket.org/vbraun/sage-virtual-appliance-buildscript). I'll > try to remember to build one for Sage 7.6 which should be out soon... > > Volker, will you have time to build it? On ask.sagemath,

[sage-devel] Re: Jupyter notebook: typeset formulas in pdf-export

Hi, Le mercredi 22 mars 2017 12:32:10 UTC+1, Daniel Krenn a écrit : > > In a Jupyter notebook, when I do > File --> Download as --> PDF via LaTeX > then typeset formulas (displayed via show(...) command) are not typeset > anymore, but displayed as their plain text output in the pdf. > > Is

[sage-devel] Re: Name symbolic expressions

This is not what you are proposing but somehow related to it: provided you consider (x,y) as coordinates on a manifold, you may define g as a named function as follows: sage: M = Manifold(2, 'M') sage: X. = M.chart() # declares the chart X on M, with coordinates (x,y) sage: g =

[sage-devel] Re: Default display for equations in notebook

To add on Travis post, some rationale for having default LaTeX typeset outputs in the Jupyter notebook is - Jupyter is scheduled to be the default notebook in Sage 8.0 - It is likely that users (especially beginners) who employ the notebook instead of the console are expecting to have "nice"

Re: [sage-devel] Sage 7.5 for Windows?

Thank you all for your answers. I've replied accordingly to the user on ask.sagemath. 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] Sage 7.5 for Windows?

Hi, On ask.sagemath.org, users keep asking for Sage 7.5 for Windows: https://ask.sagemath.org/question/36964/version-751-for-windows/ https://ask.sagemath.org/question/36601/where-can-i-find-a-windows-binary-for-sage-75-or-751/ Indeed, the latest ova file on the servers is 7.4. I understand that

[sage-devel] Re: git trac try

Thanks Paul and Volker for your answers. 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

[sage-devel] Re: git trac try

Of course I may dig into git-trac sources, but can anyone tell what "git trac try" does in terms of plain git? 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

[sage-devel] Re: Sharing my course notes "Logiciels mathématiques"

Hi Sébastien, Thank you for sharing! Best regards, 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

[sage-devel] Re: Possible bug in Maxima related to variable names in long expressions

higher than yours: Maxima 5.39.0 http://maxima.sourceforge.netusing Lisp SBCL 1.3.12 > I get > > (2*cos(a)*cos(b)-2*sin(a)*sin(b))*cos(x/2) > +2*cos(a)*sin(a)*sin(b)-2*cos(a)^2*cos(b) > > > > On Saturday, January 28, 2017 at 8:37:13 AM UTC-8, Eric Gourgoulhon wrote: >> >> Hi, &

[sage-devel] Re: Possible bug in Maxima related to variable names in long expressions

Hi, Le samedi 28 janvier 2017 19:24:01 UTC+1, Nils Bruin a écrit : > > I think it's a bug in maxima that is dependent on the ordering of the > variables. You can trigger it in maxima with exactly the same formulas, > e.g.: > > s : 2*(cos(1/2*x)*cos(y) + sin(1/2*x)^2 - 1)*(cos(z)*sin(y) + >

[sage-devel] Possible bug in Maxima related to variable names in long expressions

Hi, In Sage 7.5.1, let us consider a long (but simplifiable) trigonometric expression: sage: var('x y z') (x, y, z) sage: s = 2*(cos(1/2*x)*cos(y) + sin(1/2*x)^2 - 1)*(cos(z)*sin(y) + cos(y)* sin(z)) : *((cos(1/2*x)*cos(z) - cos(y)*cos(z) + sin(y)*sin(z))*sin(1/2*x)/(cos( 1/2*x) :

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

Le mercredi 18 janvier 2017 09:41:38 UTC+1, Dima Pasechnik a écrit : > > compiling from source might be easier and faster than trying a binary that > is not quite matching the OS. > > Yes indeed. Here are a few hints to build from source: 1/ Make sure that the prerequisites are installed on

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

Le mardi 17 janvier 2017 18:02:39 UTC+1, Sarfo a écrit : > > > > Thanks Eric > > I have download the latest binaries but I still get the same error > > Which binary have downloaded? I've tried with sage-7.5.1-Ubuntu_16.04-x86_64.tar.bz2 and it works fine for me. My system is pretty similar to

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

Hi, It seems your binary is quite old (version 7.3). Can you try again with the 7.5.1 binaries which have just been uploaded at http://www.sagemath.org/download.html Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

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

Hi Paul, Le lundi 16 janvier 2017 01:33:17 UTC+1, Paul Masson a écrit : > > Eric, it seems to me that this is now an area in which SageMath is ahead > of Mathematica, > For me, being open-source and based on Python, Sage was always ahead of Mathematica :-) More seriously, this may be true for

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

Le dimanche 15 janvier 2017 23:10:33 UTC+1, William a écrit : > > Kind of like publishing and important and foundational research paper...? > More kind of like writing a book ;-) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

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

Le dimanche 15 janvier 2017 21:24:37 UTC+1, Kwankyu Lee a écrit : > > You managed to develop SageManifolds separately from Sage, and then to > integrate the code fully with Sage. I am curious how this is done. It looks > daunting to me to chop out big code to small patches for gradual merge, >

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

The support team has just fixed the issue; the server is up again: http://sagemanifolds.obspm.fr/contrib.html Eric. Le dimanche 15 janvier 2017 20:53:08 UTC+1, Eric Gourgoulhon a écrit : > > Le dimanche 15 janvier 2017 19:59:26 UTC+1, William a écrit : > > >> 404 Not Fou

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

Le dimanche 15 janvier 2017 19:59:26 UTC+1, William a écrit : > 404 Not Found > > Indeed there is a problem on the server. I am contacting the support team... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

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

Dear Sage devs, The just released Sage 7.5 contains the integrality of SageManifolds code, the last SageManifolds tickets having been merged in 7.5.beta4 (cf. https://trac.sagemath.org/ticket/18528 ) Consequently, there is no need for a separate installation of SageManifolds (*), which is

[sage-devel] Workshop "Geometry and Computer Science"

Hi, This is to advertise this workshop taking place in Pescara (Italy) on 8-10 Feb, with at least three talks involving Sage: http://www.sci.unich.it/gncs2017/ Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

[sage-devel] Re: pynac-0.7.3 fails to build on OSX 10.12.2

Hi, Le dimanche 8 janvier 2017 23:41:35 UTC+1, Kosta a écrit : > > Hello, > > I'm trying to build 7.5.rc2 on the aforementioned platform. When getting > to pynac-0.7.3, I get an error (the first observed error during the > compilation of pynac): > > This error is fixed in 7.5.rc3 (released

Re: [sage-devel] Re: denominator() hangs on a large fraction

Le jeudi 5 janvier 2017 17:30:16 UTC+1, John Cremona a écrit : > > > It may seem heavy-handed but the final outcome is likely to be better > this way. I did a complicated computation involving a whole lot of > different number fields, mostly cyclotomic fields, and I kept on > restarting with

[sage-devel] Re: denominator() hangs on a large fraction

Le jeudi 5 janvier 2017 16:32:55 UTC+1, Dima Pasechnik a écrit : > > > we can work modulo the ideal generated by w^2+z and w'^2+z', sure, why not? > What I meant is that, suppose you start with the ring modulo the ideal generated by w^2+z and at some point in the work flow, you decide to

[sage-devel] Re: denominator() hangs on a large fraction

Le jeudi 5 janvier 2017 10:35:27 UTC+1, Dima Pasechnik a écrit : > > > Thanks for your suggestion; however, I am not sure if this could fully >> work: some computations require to take derivatives, i.e. to evaluate >> d/dx (sqrt(-z)), where z is the rational function of (x,y) discussed >>

[sage-devel] Re: denominator() hangs on a large fraction

Le mercredi 4 janvier 2017 23:41:00 UTC+1, Dima Pasechnik a écrit : > > > > On Wednesday, January 4, 2017 at 9:06:44 PM UTC, Eric Gourgoulhon wrote: >> >> Le mercredi 4 janvier 2017 21:47:00 UTC+1, Dima Pasechnik a écrit : >>> >>> >>> >

[sage-devel] Re: denominator() hangs on a large fraction

Le jeudi 5 janvier 2017 08:01:42 UTC+1, Ralf Stephan a écrit : > > There was a bug in the Pynac/Singular interface. To cancel fractions > a GCD is done via Singular. This was fixed 7 days ago in > > https://github.com/pynac/pynac/commit/fd180a9a82018e97c540950c1bbf083768f703ef > and the new

[sage-devel] Re: denominator() hangs on a large fraction

Le mercredi 4 janvier 2017 21:47:00 UTC+1, Dima Pasechnik a écrit : > > > > It's because I need to consider sqrt(-z), so that I cannot stay with >> rational functions. >> > > I woud have picked one more variable, w, and set w^2=-z. > Now everything is polynomial again... > > But z is not a

[sage-devel] Re: denominator() hangs on a large fraction

Hi Samuel, Le mercredi 4 janvier 2017 20:49:54 UTC+1, Samuel Lelievre a écrit : > > > > It's of course a good thing to track the issue, but on the other side, > why work in the Symbolic Ring? > > It's because I need to consider sqrt(-z), so that I cannot stay with rational functions. Actually

Re: [sage-devel] denominator() hangs on a large fraction

Works in Sage 7.5.beta5. So the issue has been introduced somewhere between 7.5.beta6 and 7.5.rc1... Le mercredi 4 janvier 2017 17:08:51 UTC+1, tdumont a écrit : > same for me in7.5.rc1; works in 7.4. > > > -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: denominator() hangs on a large fraction

Actually the numerator returned by Sage is not correct and trying to simplify it results in a crash + core dumped... -- 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

[sage-devel] denominator() hangs on a large fraction

Hi, In Sage 7.5.rc1: sage: var('x y') (x, y) sage: z = (x^18 + 60*x^17 + 331776*(x^2 - 1)*y^16 + 1599*x^16 + 25880*x^15 + 110 : 592*(x^4 + 15*x^3 + 99*x^2 + 485*x + 1200)*y^14 + 266700*x^14 + 160*x^ : 13 - 9216*(17*x^6 + 60*x^5 - 417*x^4 - 3040*x^3 - 13425*x^2 - 31020*x - 16 :

[sage-devel] Re: Error in compiling Sage in Ubunt 16.04u from source

Le vendredi 23 décembre 2016 15:12:08 UTC+1, Fjordforsk A/S a écrit : > > Hi, installing python-pip did not solve it. > > Have you tried typing make distclean before running make? Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] Re: Error in compiling Sage in Ubunt 16.04u from source

Hi, Le jeudi 22 décembre 2016 18:15:27 UTC+1, Fjordforsk A/S a écrit : > > rectory > [pip-8.1.2.p1] /home/sem/Downloads/sage-7.4/local/bin/python: No module > named pip > Most probably you can fix this by installing the Ubuntu package python-pip. Best wishes, Eric. -- You received this

Re: [sage-devel] Re: [sage-notebook] Re: Proposal: move SageNB back to Sage

Hi Nicolas, Le mercredi 23 novembre 2016 22:46:34 UTC+1, Nicolas M. Thiéry a écrit : > > > I have been using Jupyter locally for my teaching since two years, and > am very happy with it. The only missing features have been migration > tool from sagenb and interacts; both are on their way. > >

[sage-devel] Re: 7.5.beta1 build hands at building docs

Could it be some memory issue ? Building the doc requires a lot of memory: typically with only 4 GB of RAM, it uses swap, which makes the process quite slow. How long have you waited before hitting Crtl-C ? Eric. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Issue with figures in doc.sagemath.org

Le jeudi 3 novembre 2016 17:50:44 UTC+1, Harald Schilly a écrit : > > > That's taken care of > 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] Issue with figures in doc.sagemath.org

Hi, Some 3D figures of the inline reference manual are not displayed on http://doc.sagemath.org/html/en/reference/ They are replaced by something like ../../../_images/parametric_plot3d-1.png See for instance

[sage-devel] Re: jsmol.js

Hi, A related note: there is ongoing work at https://trac.sagemath.org/ticket/12402 to use three.js for 3d graphics in Sage, especially in Jupyter notebook. It is almost ready and has already features far superior to jsmol (e.g. axes labels). Hopefully, it could be merged in Sage 7.5. Then, we

[sage-devel] Re: sage's increasingly long startup time?

Le jeudi 27 octobre 2016 21:22:23 UTC+2, Eric Gourgoulhon a écrit : > > Hi, > > Which computer are you using? On my 5-years old laptop (Core i5-2410M + 4 > GB memory), it takes "only" 22 seconds. Running a second *time* takes 1.4 > second. > > Best regards,

[sage-devel] Re: sage's increasingly long startup time?

Hi, Which computer are you using? On my 5-years old laptop (Core i5-2410M + 4 GB memory), it takes "only" 22 seconds. Running a second takes 1.4 second. Best regards, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] Re: trac down?

Le samedi 22 octobre 2016 15:16:40 UTC+2, William a écrit : > > Hi, > > I recreated trac on a VM with much, much more RAM and cpu. It seems > to be working well now. > Thank you very much! Indeed it works well. Eric. -- You received this message because you are subscribed to the Google

Re: [sage-devel] Re: trac down?

Hi, >From France, it seems that we still cannot connect to https://trac.sagemath.org/ while the rest of Internet seems OK (including http://www.sagemath.org/ and github). I could push a new commit to trac though (the response was very slow but it seemed to have worked). Eric. Le vendredi 21

<    1   2   3   4   5   6   7   >