[sage-devel] Sage 5.10 : (unfathomable) problem compiling singular.

Trying to compile sage on an old laptop (Toshiba Core2 + 2 Gb RAM + Debian testing). I'm compiling with MAKE=make -j2 -l 3. End of the (second attempt to) compilation : === g++ -O2 -g -fPIC -pipe -fno-implicit-templates

[sage-devel] Re: Sage 5.10 : (unfathomable) problem compiling singular.

.spkg Thanks a lot ! Compiling now... Emmanuel Charpentier -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- You received this message because you are subscribed to the Google Groups sage-devel group

Re: [sage-devel] Google Summer of Code

Aaarghh... nobody took up the port of Rubi to Sage. Too bad for the engineering type users of sage, for which this class of problems is important. Anyone having an idea for promoting this ? -- Emmanuel Charpentier Le mardi 22 avril 2014 15:40:55 UTC+2, William a écrit : On Tue, Apr 22, 2014

[sage-devel] Re: RAM to build Sage

. indeed. Please review :) http://trac.sagemath.org/ticket/15921 What is the goal ? Sage runing natively on mobile phones/tablets ? Yay !! -- Emmanuel Charpentier On Friday, May 9, 2014 1:41:44 PM UTC+2, mmarco wrote: Well, testing, for instance, if everything runs in an ARM

[sage-devel] Need of handholding : how to update a standard package ?

3.0.2, but I do nit know how to fix it. A bit of helping hand would be useful. PS I did not (yet) create a track ticket to make this officuial : I wanted first to check that I was able to create the patch. -- Emmanuel Charpentier -- You received this message because you are subscribed

[sage-devel] Re: network access from projects

Some access to CRAN might be useful to statisticians misguided enough to use sage from their accounts ? Alternative : az local CRAN mirror (but that's large and unwidely...). For biologists : genome/proteome banks ? -- Emmanuel Charpentier Le jeudi 19 juin 2014 19:57:06 UTC+2, William a écrit

[sage-devel] Re: Need of handholding : how to update a standard package ?

years... Better late than never !). -- Emmanuel Charpentier Le jeudi 3 juillet 2014 00:15:32 UTC+2, Volker Braun a écrit : My guess would be that you have another sage in the path, and when you run sage -sh sage-fix-pkg-checksums then you recompute the checksums for that installation. Run

[sage-devel] R 3.1 for sage

R 3.1 for sage (trac#16611 http://trac.sagemath.org/ticket/16611) awaits your review. Due to the existence of specificities on arm, OS/X and cygwin, those three platforms need to be tested. -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: R 3.1 for sage

delaying package upgrades with some additional manual steps. On Thursday, July 3, 2014 2:33:06 PM UTC-4, Emmanuel Charpentier wrote: R 3.1 for sage (trac#16611 http://trac.sagemath.org/ticket/16611) awaits your review. Due to the existence of specificities on arm, OS/X and cygwin, those

Re: [sage-devel] Re: network access from projects

... -- Emmanuel Charpentier -- 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

[sage-devel] build system : a (smallish) bug when adding/updatng a package.

knowledge of sage's build system than I have. HTH, -- Emmanuel Charpentier -- 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

[sage-devel] Re: Please review Python 2.7.8 update

Done. Seems good. -- Emmanuel Charpentier Le dimanche 13 juillet 2014 06:53:50 UTC+2, Volker Braun a écrit : == Trac #16648: Python 2.7.8 New tarball: http://boxen.math.washington.edu/home/vbraun/upstream/python

[sage-devel] Re: weird integral behavior

).simplify_full()) gee(t)=bar(t,t) limit(gee(t),t=1) The expression for bar is atrocious. bit the limit is not : 1/2*I/pi By the way : gee(1) gives : -1/2*I/pi indeed. But: integrate(integrate(foo(x,y),y,0,1),x,0,1) gives : 0 -- Emmanuel Charpentier Both Mathematica and Maple give 0

[sage-devel] Re: weird integral behavior

arguments: no canonical coercion from type 'tuple' to Symbolic Ring A possible enhancement ? HTH, -- Emmanuel Charpentier Anne -- 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: Upper case letters in Sage Notebook

)) exceptions.LookupError: no user 'V_2e' HTH, -- Emmanuel Charpentier Meanwhile in the console log I can see the following message: 2014-07-22 20:01:15+0300 [-] WSGI application error Traceback (most recent call last): File

[sage-devel] Curious problem with Sage fat_binary tarballs

I have yet another example of the brittleness of Sage binaries. See trac#16694 http://trac.sagemath.org/ticket/16694 for details. Roughly, a binary compiled with SAGE_FAT_BINARY=yes gives a defective Sage's R on a machine differing from the original one. I may have another one in preparation

[sage-devel] Re: Curious problem with Sage fat_binary tarballs

Le mercredi 23 juillet 2014 22:59:54 UTC+2, Jean-Pierre Flori a écrit : SAGE_FAT_BINRAY is quite fragile. If you really want me to, I can break it on quite every system. Are the machine really different? Yes. I have a good laptop (core I7, 16 GB RAM), but my pinchy employer insists on me

[sage-devel] Re: Curious problem with Sage fat_binary tarballs

Le jeudi 24 juillet 2014 01:38:54 UTC+2, kcrisman a écrit : SAGE_FAT_BINRAY is quite fragile. If you really want me to, I can break it on quite every system. Are the machine really different? Maybe its just a problem with R and can be fixed. I think that is quite likely and could be

[sage-devel] Yet another update ro Sage's R

The R core group has released R 3.1.1, which seems to be mostly a bugfix. This new version is ported to sage by trac#16711 http://trac.sagemath.org/ticket/16711, which await your reviews. HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google

[sage-devel] Re: What should be the present working directory for sage -notebook=ipython ?

import your worksheet (seems to be a compressed archive of a directory tree), and to explicitely export it after saving it. HTH, -- Emmanuel Charpentier Le lundi 13 octobre 2014 15:25:01 UTC+2, Sébastien Labbé a écrit : Hi sage-devel, At http://trac.sagemath.org/ticket/16996#comment:47, we had

[sage-devel] New (unexpected, and, as far as I know, undocumented) behaviour of graphics ?

, thus opening an external viewer, but one gets a static view by default, and the doc of the default viewer (to be able to change the point of view) is pretty elusive... - A way to view() various objects not involving an external \LaTeX document. HTH, -- Emmanuel Charpentier

[sage-devel] Re: New (unexpected, and, as far as I know, undocumented) behaviour of graphics ?

nothing ; tachyon a very faint png image in a separate image viewer. HTH, -- Emmanuel Charpentier -- 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

[sage-devel] Re: Can We Trust Computer Algebra Systems?

, economists, I'm looking at you : Forty years of unexpected consequences and still no incentive to revise your postulates... -- Emmanuel Charpentier Le dimanche 26 octobre 2014 16:46:54 UTC+1, rjf a écrit : This article is also discussed in another thread .. Trio . . Depending on what you

[sage-devel] Git weirdness ?

/752190c8b5dcd7964ddbae59a4f7899100d787be I *suppose* that my tree is now *correctly* at RC1, and I'll try to compile it (overnight : this is a small and slow machine...). Still, it's scary : I can't make sense of the message... HTH, -- Emmanuel Charpentier -- You received this message because you

Re: [sage-devel] Git weirdness ?

on this. Anyway : My tree still is at rc0 : make just rebuilt the docs (which was already up to date). Currently re-making after git pull trac develop ... results overnight. [ Snip ...] Sincerely, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google

[sage-devel] Re: Git weirdness ?

) to get rid of it right now. I followed Vincent's suggestion gefore seeing your answer. It seems to have been efficient. Thank you (again). -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop

[sage-devel] Please review R's upgrade to 3.1.2

. It already passes make ptestlong. HTH, -- Emmanuel Charpentier -- 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: When/by who/how was the code of conduct initiated ?

civility through linguistic tools). Hoping (but not really expecting) this helps, -- Emmanuel Charpentier Cheers, Simon -- 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: When/by who/how was the code of conduct initiated ?

7 Frimaire an 223 de la Révolution die, scribit Volker Braun : On Thursday, November 27, 2014 7:20:42 PM UTC, Emmanuel Charpentier wrote: Alternative : make the majestuous Latin of Leonard Euler the lingua franca of sage- lists/groups. That would give us the added benefit of having

Re: [sage-devel] Re: Maple versus Mathematica

worth the work...), I'd try my hand to it. HTH, -- Emmanuel Charpentier -- 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

Re: [sage-devel] Re: Maple versus Mathematica

Le lundi 1 décembre 2014 21:23:55 UTC+1, vdelecroix a écrit : It is open source document... so the sources are on the web (and advertised on the main webpage http://sagebook.gforge.inria.fr/) http://dl.lateralis.org/public/sagebook/sagebook-1.0.tar.bz2 I was aware of this one : it is

[sage-devel] Re: fricas pkg in Sage

option to integrate(), which seems a very good idea. Nevertheless, having a fricas package which might replace a systemwide fricas installation might help its disemination. HTH, -- Emmanuel Charpentier Le samedi 6 décembre 2014 18:23:32 UTC+1, vdelecroix a écrit : Hello, I just discover

Re: [sage-devel] Re: What are we unable to do right now ?

Regards, That interface calls a systemwide fricas. This works for me... HTH, -- Emmanuel Charpentier -- 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-devel] Re: What are we unable to do right now ?

be the point of the whole exercise... HTH, -- Emmanuel Charpentier -- 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: fricas pkg in Sage

Le samedi 6 décembre 2014 19:01:46 UTC+1, Emmanuel Charpentier a écrit : I'm not sure that fricas *has* to be a package : the current versins (6.4, 6.5beta) already have the fricas interface compiled in : /usr/local/sage-6.5/src/build/lib.linux-x86_64-2.7/sage/interfaces/fricas.py /usr

[sage-devel] Re: User Survey

How do you reach your estimate of 16 Wh/Google search ? Any source ? -- Emmanuel Charpentier Le lundi 8 décembre 2014 14:44:55 UTC+1, parisse a écrit : Le vendredi 5 décembre 2014 21:14:54 UTC+1, maldun a écrit : I don't think that the functionality of Sage is the big problem, in fact

[sage-devel] Comment on trac#17234 (unpostable via Trac.sagemath.org)

needs work ? --- HTH, -- Emmanuel Charpentier -- 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: Trac #17852 hangs

Logged out successfully. Logged back in successfully. I could retype my comment (paste it in fact), but the ticket got locked as soon as I tried to preview it. Il'' try to retype it and submit it without previewing. HTH, -- Emmanuel Charpentier Le lundi 2 mars 2015 22:53:54 UTC+1, Emmanuel

[sage-devel] Re: Trac #17852 hangs

Got locked as soon I hit Submit changes. Damn. I'll post the comment in sage-devel on a new thread. -- Emmanuel Charpentier Le lundi 2 mars 2015 22:59:30 UTC+1, Emmanuel Charpentier a écrit : Logged out successfully. Logged back in successfully. I could retype my comment (paste it in fact

[sage-devel] Re: Trac #17852 hangs

to break the lock. I'll answer to this post if this is unsuccessful. HTH, -- Emmanuel Charpentier Le mercredi 25 février 2015 19:15:41 UTC+1, Jeroen Demeyer a écrit : I am unable to make any change to Trac #17582: trac just hangs forever when I try to change the status to needs_work or add

[sage-devel] Re: Comment on trac#17234 (unpostable via Trac.sagemath.org)

permissions in SAGE_LOCAL/share/sage/ext/doctest On Monday, March 2, 2015 at 11:09:29 PM UTC+1, Emmanuel Charpentier wrote: This was intended to be a comment on Trac#17234 http://trac.sagemath.org/ticket/17234, but I was unable to post it on theright place (see this thread). https

[sage-devel] Re: Comment on trac#17234 (unpostable via Trac.sagemath.org)

Thank you. This explains that. FYI : I had to re-build from scratch. I don't understand why... yet ! Thanks a lot ! -- Emmanuel Charpentier Le mardi 3 mars 2015 21:41:42 UTC+1, Volker Braun a écrit : When closing a ticket, a script replaces the branch on the trac ticket (which might

[sage-devel] Why packages tarballs have to be in lowercase ?

are broken by mixedCased tarballs ? 2. Is this restriction really necessary ? HTH, -- Emmanuel Charpentier -- 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

[sage-devel] Re: Why packages tarballs have to be in lowercase ?

should *not* rely on them. HTH, -- Emmanuel Charpentier Le jeudi 30 avril 2015 08:57:57 UTC+2, Emmanuel Charpentier a écrit : The Developer's guide http://www.sagemath.org/doc/developer/packaging.html#directory-structure states the ported packages' tarballs have to be in *lower case

[sage-devel] Re: Please review trac#18229.

After the closing of a Mac Xcode problem (trac#18254 http://trac.sagemath.org/ticket/18254), trac#18229 http://trac.sagemath.org/ticket/18229, which now upgrades R to 3.2.0, needs review (again). HTH, -- Emmanuel Charpentier Le jeudi 16 avril 2015 22:49:52 UTC+2, Emmanuel Charpentier a écrit

[sage-devel] Please review trac#18229.

Small change ticket : upgrade R to 3.1.3. That's trac#18229 http://trac.sagemath.org/ticket/18229. HTH, -- Emmanuel Charpentier -- 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

Re: [sage-devel] Re: Extremely broad bug in Sage Integral Computations

. Any ideas ? HTH, -- Emmanuel Charpentier Le mercredi 3 juin 2015 19:47:52 UTC+2, Bill Page a écrit : Yes. https://cloud.sagemath.com/projects/b04b5777-e269-4c8f-a4b8-b21dbe1c93c6/files/integral.sagews On 3 June 2015 at 13:31, Samuel Lelievre samuel@gmail.com javascript: wrote

[sage-devel] Trac#18691 needs your attention (specially if you have a Mac...).

trac#17572 http://trac.sagemath.org/ticket/17572 to Darwin OS, but I need your input to propose a real solution. So if you have a few minutes (hours ?) in your copious free time, I'm eager for your ideas... -- Emmanuel Charpentier http://trac.sagemath.org/ticket/17572 -- You received

[sage-devel] Trac#18820 needs review

Trac#18820 http://trac.sagemath.org/ticket/18820# updates R to 3.2.1. This trivial patch needs your attention. HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails

[sage-devel] What in Sage uses Boost ? And who maintains it ?

(a diabolically efficient MCMC sampler), which needs Boost>=1.58. See this thread on stan-users <https://groups.google.com/forum/#!topic/stan-users/XygoXG0SoTM> for details. Hence two questions : 1) What in Sage uses Boost ? 2) Is someone maintaining it ? Sincerely yours, --

[sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

Debian and Ubuntu) and other packages (including R) are up to now). Porting the whole of Boost should also be considered, but maybe after considering what uses the non-headers parts of Boost. AFAICT, The R package is headers-only. HTH, -- Emmanuel Charpentier Le mercredi 11 novembre 2015 13:06:21

[sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

I ported 1.58.0 headers in Trac #19582 <http://trac.sagemath.org/ticket/19582>, which needs review. HTH, __ Emmanuel Charpentier Le vendredi 13 novembre 2015 07:38:53 UTC+1, Emmanuel Charpentier a écrit : > > FYI, > > Just for the hell of it, I *did* update boost

[sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

ich is distributed via @#!&! Sourceforge and therefore has no stable URL... I'll try to do that "à l'ancienne"... HTH, -- Emmanuel Charpentier > to download the tarball and update the relevant configuration files in Sage > > > > On Wednesday, November 1

Re: [sage-devel] Re: What in Sage uses Boost ? And who maintains it ?

nd. The ticket I opened to update this library has been closed. Therefore, I won't touch it. HTH, -- Emmanuel Charpentier Le mercredi 11 novembre 2015 21:30:22 UTC+1, François a écrit : > > There is a ticket with a more recent boost: > http://trac.sagemath.org/ticket/17966 > > It bas

[sage-devel] Re: Mathematics without apologies - Portrait of a Problematical Vocation

ntly ill-understood because we do not think about them with the right structures... ] The same thing could be said, *mutatis mutandis,* about the teaching of history, humanities, foreign languages, literature and philosophy. Hope this helps (but deeply doubt it...), -- Emmanuel Charpenti

Re: [sage-devel] Request for advice : extending/reimplementing the R interface with RPy2 ?

availability of graphics seemed for a time to depend of the availability of an R installation in the client machine (see Trac#14071 <http://trac.sagemath.org/ticket/14071> for details). Nowadays, we get only the "missing picture" icon... if used on (from) a machine without R i

Re: [sage-devel] Request for advice : extending/reimplementing the R interface with RPy2 ?

Thanks, I missed this one (I searched for "r-project"). Well, you can add a dependency on rpy2 younger than 2.3.2 (the current 2.7.4 whic I propose in Trac#19638 <http://trac.sagemath.org/ticket/19638> does the job. HTH, -- Emmanuel Charpentier Le dimanche 13 décembre 201

[sage-devel] Request for advice : extending/reimplementing the R interface with RPy2 ?

o your keyboards... -- Emmanuel Charpentier -- 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

[sage-devel] Re: Jupyter notebook by default?

Le dimanche 3 janvier 2016 21:23:56 UTC+1, Volker Braun a écrit : > > On Sunday, January 3, 2016 at 5:36:30 PM UTC+1, Emmanuel Charpentier wrote: >> >> [ BTW : that's not really a bug, but rather a design conflict : the >> original %mode functions were designed to s

[sage-devel] Re: Jupyter notebook by default?

orksheets). Yet another interact interface ? That might be interesting if and only if the "new" interface has significantl enhancements over the "old" one... HTH, -- Emmanuel Charpentier > > Jonathan > > On Saturday, January 2, 2016 at 6:15:01 PM UTC-6, Vol

[sage-devel] Re: Jupyter notebook by default?

of code and prompts won't load() cleanly from a file ('indentation error'). HTH, -- Emmanuel Charpentier -- 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 a

[sage-devel] Re: trouble with packages

format). Maybe we should bug Ivan Andrus to get this feature back ? I am still a big fan of sage_mode for some uses, but find myself more and more using the Jupyter notebook. And, anyway, when I converge to something communicable, my work usually ends up in a .tex file with a proeminent \

[sage-devel] Re: Jupyter notebook by default?

Dear Volker, Le dimanche 3 janvier 2016 16:33:36 UTC+1, Volker Braun a écrit : > > On Sunday, January 3, 2016 at 2:41:51 PM UTC+1, Emmanuel Charpentier wrote: >> >> >>- "other language" cells : %maxima and %r (possibly other >>interpreters such a

[sage-devel] Re: Jupyter notebook by default?

book "solution" (one worksheet, a $#!+load of anonymous files hidden in an invisble directory). Hoping that my two cents may help, -- Emmanuel Charpentier Le vendredi 18 décembre 2015 11:35:53 UTC+1, Jeroen Demeyer a écrit : > > Should the Jupyter notebook be the default notebook for t

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

he Debian developer oversaw the necessity of synchronizing the updates of the linker and binutils... and I'll refrain from commenting. HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Request for advice : upgrading a standard package requires a new package

how to proceed... A third solution would e to silently include singledispatch in the source to rpy2. This "solution" seems toguarantee future incompatibilities. What should I do ? Bonus question : how to package rpy2 to signal that it depends on singleispatch ? HTH, -- Emmanuel Charpe

Re: [sage-devel] Request for advice : upgrading a standard package requires a new package

A preliminary version is available at Trac#19638 <http://trac.sagemath.org/ticket/19638>. It seems that %rmagic (now %load_ext rpy2.ipython ; %R ; %%R) does not exist in the documentation. Where should I write it and point to the (existing) help pages ? HTH, -- Emmanuel Charpentier Le

[sage-devel] Re: Git message while pushing a patch

Thank you ! I'll look that up in git's doc. -- Emmanuel Charpentier Le mardi 5 avril 2016 09:39:20 UTC+2, Volker Braun a écrit : > > Pruning is about unreachable objects (commits not referenced by a branch, > e.g. because you deleted the branch). It is safe to do unless you >

[sage-devel] Git message while pushing a patch

Pushing to Trac#20190 , I got : charpent@asus16-ec:/usr/local/sage-exp$ git trac push Pushing to Trac #20190... Guessed remote branch: u/charpent/upgrade_r_to_3_2_4 remote: Trac #20190: Commit changed to feb037. Auto packing the repository for

[sage-devel] Git : need help with Trac#22189 : I can't solve a merge conflict with 7.6beta1

th 7.6.beta1. I squashed the two commits in one and forced an update. The merge with 7.6.beta1 is still impossible without manual intervention. Could some king suol point me to an answer to two simple questions : 1. Where did goof ? 2. How to solve that ? Sincerely, -- Emmanuel Charp

Re: [sage-devel] For the record : the lil' Win10 notebook that (almost) could (barely).

Dear William, Le jeudi 16 février 2017 08:45:36 UTC+1, William a écrit : > > On Wed, Feb 15, 2017 at 11:26 PM, Emmanuel Charpentier > <emanuel.c...@gmail.com > wrote: > > Dear list, > >[...] > > The trade-offs are not obvious. No solution dominates the

[sage-devel] For the record : the lil' Win10 notebook that (almost) could (barely).

or ppa would have spared me this, but I wanted to assess the complication of the whole process) - with a penalty in terms of disk I/O - with acceptable results - with the possibility of adding optional packages The trade-offs are not obvious. No solution dominates the othe

[sage-devel] The end of our current R saga ? Reviews needed.

h R >= 3.3.x. For docudrama lovers, the next cliffhanger should be a future Rpy2-based R interface ;-). But don't hold your breath... HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

[sage-devel] Re: Database_gap broken ?

That log is attached to the first message of this thread. BTW, it is suspiciously short... Should I try to force a reinstallation ? -- Emmanuel Charpentier Le dimanche 19 février 2017 19:37:08 UTC+1, Dima Pasechnik a écrit : > > Your log contains a lot of stuff like > >

[sage-devel] Re: Database_gap broken ?

Le dimanche 19 février 2017 20:34:57 UTC+1, Emmanuel Charpentier a écrit : > > > > Le dimanche 19 février 2017 19:54:06 UTC+1, Dima Pasechnik a écrit : >> >> >> >> On Sunday, February 19, 2017 at 6:42:07 PM UTC, Emmanuel Charpentier >> wrote: >>

[sage-devel] Re: Database_gap broken ?

Le dimanche 19 février 2017 19:54:06 UTC+1, Dima Pasechnik a écrit : > > > > On Sunday, February 19, 2017 at 6:42:07 PM UTC, Emmanuel Charpentier wrote: >> >> That log is attached to the first message of this thread. BTW, it is >> suspiciously sh

Re: [sage-devel] Database_gap broken ?

Le dimanche 19 février 2017 12:58:40 UTC+1, Emmanuel Charpentier a écrit : > > Indeed, I didn't install gap_packages. I'll install it and retest later > this afternoon... > Alas... It's worse : -- sage -t --long src

Re: [sage-devel] Database_gap broken ?

Indeed, I didn't install gap_packages. I'll install it and retest later this afternoon... -- Emmanuel Charpentier Le 19 févr. 2017 12:55, "Dima Pasechnik" <dimp...@gmail.com> a écrit : > could it be that you did install database_gap, but no gap_packages? > We probably onl

Re: [sage-devel] For the record : the lil' Win10 notebook that (almost) could (barely).

Dear Erik, Le jeudi 16 février 2017 11:09:00 UTC+1, Erik Bray a écrit : > > On Thu, Feb 16, 2017 at 8:26 AM, Emmanuel Charpentier > <emanuel.c...@gmail.com > wrote: > > Dear list, > > > > This is a followup on the threads dedicated to the alternatives

[sage-devel] Re: R fails to compile

Forgot to add : ISTR that R has depended on an external iconv for a long while. I didn't see it would now be mandatory... -- Emmanuel Charpentier Le mercredi 18 janvier 2017 14:15:57 UTC+1, Emmanuel Charpentier a écrit : > > Do you have iconv installed systemwide ? > > Le mardi 17

[sage-devel] Re: R fails to compile

Do you have iconv installed systemwide ? Le mardi 17 janvier 2017 03:24:54 UTC+1, Rob Gross a écrit : > > Hi, > > I tried to upgrade to 7.5.1 on several different Macs which I thought had > identical software. > > However, on one of them, R failed to compile, with the error: > > installing

Re: [sage-devel] Re: Our SSL serial drama-cum-cliffhanger

I'm not sure to understand the ticket. Does that means that OS X Sage will depend on Apple's SSL library ? Or depend on a systemwide OpenSSL ? Or am I mistaken entirely ? -- Emmanuel Charpentier Le lundi 16 janvier 2017 21:07:40 UTC+1, Kosta a écrit : > > Regarding OSX, take a look at

[sage-devel] Re: Current Maxima version

I added a reminder about this problem on #22191... HTH, -- Emmanuel Charpentier Le mercredi 18 janvier 2017 19:47:37 UTC+1, Dima Pasechnik a écrit : > > I can confirm that this example also works on Maxima 5.39.0 running on > SBCL 1.3.12. > (I thought for a moment that it's a reg

Re: [sage-devel] Where is implemented the logic deciding whether to install git or not ?

Thank you very much ! -- Emmanuel Charpentier Le lundi 16 janvier 2017 09:01:26 UTC+1, François a écrit : > > line 292 to 297 of configure.ac. > > François > > > On 16/01/2017, at 20:58, Emmanuel Charpentier <emanuel.c...@gmail.com > > wrote: > > >

[sage-devel] Where is implemented the logic deciding whether to install git or not ?

Dear list, The git standard package is not installed when the system on whic Sage is built has a systemwide version of git. I have been unable to find where the logic of this decision is implemented. Can some kind soul point me to this place ? Sincerely, -- Emmanuel Charpentier -- You

[sage-devel] Re: Current Maxima version

s://trac.sagemath.org/wiki/symbolics>. HTH, -- Emmanuel Charpentier Le mercredi 18 janvier 2017 13:31:21 UTC+1, Dima Pasechnik a écrit : > > ticket upgrading Maxima tp 5.39.0 is ready for review now: > https://trac.sagemath.org/ticket/18920 > > On Monday, November 28,

Re: [sage-devel] Re: R fails to compile

It also used to build pcre, an lzma library and SSL tools. No longer since 3.3, which is an itch I tried to scratch for 8 months... Hence also my insistence on the SSL tragicomedy. -- Emmanuel Charpentier Le 18 janv. 2017 19:32, "Jean-Pierre Flori" <jpfl...@gmail.com> a écrit :

[sage-devel] [Yet again] Sage's R vs system's R

While trying my hand at porting R 3.3.1 to Sage (needs_review, by the way), I found this in the current R Installation and Administration manual : > C.8 Cygwin > > The 32-bit

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

executing "git fetch trac public/21135" STDERR: fatal: Couldn't find remote ref public/21135 I do not understand this error. This never happened to me before. Ideas ? -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-deve

[sage-devel] Re: [Yet again] Sage's R vs system's R

Le samedi 20 août 2016 19:46:45 UTC+2, Jean-Pierre Flori a écrit : > > > > On Saturday, August 20, 2016 at 7:44:15 PM UTC+2, Jean-Pierre Flori wrote: >> >> >> >> On Saturday, August 20, 2016 at 7:05:27 PM UTC+2, leif wrote: >>> >>> Emmanuel

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

Le dimanche 21 août 2016 01:33:57 UTC+2, leif a écrit : > > Emmanuel Charpentier wrote: [ Snip...] > > > No. Works for me: > > $ git fetch -v trac public/21135 && echo OK > remote: Counting objects: 2875, done. > remote: Compressing objects: 100% (113

[sage-devel] Re: Good news on the Windows/Cygwin front

Could you have a look at Trac#20523 ? This trivial update bangs on a missing dependency on Cygwin... Le lundi 22 août 2016 11:19:38 UTC+2, Erik Bray a écrit : > > Hi all, > > Here is the result of my latest run of `./sage -t -a` on Cygwin 64-bit: > > $

[sage-devel] Re: [Yet again] Sage's R vs system's R

>From Trac#20523 : Replying to [comment:9 tscrim]: > I get a failure trying to install this on Cygwin32 with > {{{ > checking for lzma_version_number in -llzma... no > configure: error: "liblzma library and headers are required" > Error configuring R. >

[sage-devel] Re: integration algorithms

A few points : 1. Sympy has interesting answers in some cases. But : 1. It often offers responses as conditional expressions (akin to Mathematica's lists of tuples (expression, rule)), whic we don't (yet ?) know how to handle ; 2. It often uses special functions not

[sage-devel] Re: integration algorithms

Sorry : I've been interrupted at the wrong omment... Le lundi 27 février 2017 18:13:33 UTC+1, Emmanuel Charpentier a écrit : > > A few points : > >1. Sympy has interesting answers in some cases. But : > 1. It often offers responses as conditional ex

[sage-devel] Re: [Yet again] Sage's R vs system's R

nually" (=explicitly) install it then (or in the > future, perhaps have to configure Sage '--with-R' or something like that). > (Wouldn't that be "sage -i R" ? ) Indeed. Yet another chore during Sge maintainance easily avoided with standard R binary, partially avoide

[sage-devel] Re: [Yet again] Sage's R vs system's R

Well... Tha was ... instructive ... We see to have two consistent options to keep R a standard package : 1. Keep R as a standard package, including the binaries. This involves : - make xz a standard package ; - port the old-style pcre package as a new-style standard package ;

[sage-devel] To the attention of Nicolas M Thiéry (recursive-monkey-patch)

il from your instructions. Thanks in advance, -- Emmanuel Charpentier -- 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 po

Re: [sage-devel] To the attention of Nicolas M Thiéry (recursive-monkey-patch)

Thanks a lot for this prompt answer. That's what I was afraid of : to add methods to sage.symbolic.expression.Expression, you jus have to patch the source and recompile. That means a turnaround time of 10-40 minutes each time. Better be sure of my syntax... -- Emmanuel Charpentier Le

Re: [sage-devel] To the attention of Nicolas M Thiéry (recursive-monkey-patch)

age. Agaon, do you have a list ? -- Emmanuel Charpentier -- 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

  1   2   3   4   5   6   >