Re: [sage-devel] Re: Citing used Sage components automatically

2011-07-30 Thread Benjamin Jones
On Fri, Jul 29, 2011 at 7:50 AM, Niles wrote: > > Indeed, one of the things that first piqued my curiosity was the > message when quitting a Sage session: "Exiting spawned Maxima > process." or "Exiting spawned Gap process."  Another approach to > raising user awareness might be to have each compo

Re: [sage-devel] Re: Citing used Sage components automatically

2011-07-28 Thread John Cremona
> > > I find the two responses here very interesting.  From Niles and John's > responses, it sounds like this feature could help users turn into developers > as their curiosity about the algorithms gets the better of them and they > started poking around in the internals of Sage. > Would it be pos

Re: [sage-devel] Re: Citing used Sage components automatically

2011-07-28 Thread John Cremona
Interesting! I ran this on my script which takes elliptic curves as computed by eclib (outside Sage, that's a C++ program which already uses gmp, NTL, pari) and got this list: ['PARI', 'mwrank', 'MPFI', 'Singular', 'FLINT', 'MPFR', 'ginac', 'GMP', 'Magma', 'NTL'] This does not include sympow (wh

Re: [sage-devel] Re: Citing used Sage components automatically

2011-07-27 Thread William Stein
On Wed, Jul 27, 2011 at 10:48 AM, Jason Grout wrote: > On 7/27/11 10:08 AM, Andrey Novoseltsev wrote: >> >> To get these lists, it seems to me that one can execute the code >> "f(75)" in a profiler, collect used functions, and then look for >> substrings (either modules or particular functions) fr

Re: [sage-devel] Re: Citing used Sage components automatically

2011-07-27 Thread Mike Hansen
On Wed, Jul 27, 2011 at 10:48 AM, Jason Grout wrote: > IIRC, someone (Mike Hansen, I believe) wrote something that would track > pexpect interfaces or something to see what software was being used.  I > cannot find the command name for his function, though. > sage: from sage.misc.citation import