[sage-devel] Re: Proposal: Deprecate all of sage.finance, sage.media, sage.stats in 9.1

Did you mean 9.2? It's too late to add deprecations to 9.1, in my opinion. On Friday, May 1, 2020 at 2:19:32 PM UTC-7, Matthias Koeppe wrote: > > These modules have a very limited amount of code, seem to have seen no > major development for about 10 years, and are (with minor exceptions) > unus

[sage-devel] Re: Want to add generalised Newton's method for solving a nonlinear systems of equations to Sage

Sorry forgot to give details on the algorithm I want to add. Here's a Wikipedia link o n the subject. To summarise, it's an iterative numerical method, similar to sage.numerical.optimize.find_root

[sage-devel] Want to add generalised Newton's method for solving a nonlinear systems of equations to Sage

Hello, I have a generalised implementation of Newton's method for solving a nonlinear system of equations that I want to add to Sage. This would be my first potential contribution so I had a few questions before I can move forward. Questions #1: The reason I wrote an implementation was because

[sage-devel] Proposal: Deprecate all of sage.finance, sage.media, sage.stats in 9.1

These modules have a very limited amount of code, seem to have seen no major development for about 10 years, and are (with minor exceptions) unused in the rest of Sage. Potential users will be better off with looking for mainstream libraries in the Python ecosystem, or with interfacing with Pyt

Re: [sage-devel] remove log_html() and other log_*()

> > > > So before deprecating, consider points of view of users from different > backgrounds. We hope that mathematicians are using Sage, and we shouldn't > require them to know about "grep". Don't get me wrong, grep is great and I > use it all the time, but I bet that many of my colleagues don

Re: [sage-devel] remove log_html() and other log_*()

There is a tradeoff. If I want to search the Sage source code, running "search_src(...)" in Sage is easy, and it's in our documentation, so people might find it. Running '!grep -R -n ... "$SAGE_ROOT"/src/sage' is not quite as easy; if you want the line numbers, you need -n, and it also requires

Re: [sage-devel] Re: Unable to build ecl-16.1.2.p5 on Ubuntu 20.04 LTS

All, please feel free to update the version-specific installation FAQ at https://wiki.sagemath.org/ReleaseTours/sage-9.0 On Friday, May 1, 2020 at 1:02:10 AM UTC-7, Dima Pasechnik wrote: I suppose a canonical way to build would be > > > ./configure --without-system-libffi > make > > > On Fri

Re: [sage-devel] remove log_html() and other log_*()

I would be in favour of deprecation and eventual removal of search_src() just as we discard old implementations of maths functions in favour of maintained faster implementations in external libraries, we ought to discard outdated interfaces too. Dima On Fri, 1 May 2020, 14:22 Michael Orlitzky,

Re: [sage-devel] remove log_html() and other log_*()

On 5/1/20 8:45 AM, kcrisman wrote: > > I don't know whether python functions can call the ! things but I > think it would help users to keep search_src(s) as a shorthand for > !grep -r s $SAGE_ROOT/src and search_def(s) for search_src("def "+s). > > > Thanks for more calmly and conci

Re: [sage-devel] remove log_html() and other log_*()

> I don't know whether python functions can call the ! things but I > think it would help users to keep search_src(s) as a shorthand for > !grep -r s $SAGE_ROOT/src and search_def(s) for search_src("def "+s). > > Thanks for more calmly and concisely making my point for me. As for a relevant x

Re: [sage-devel] remove log_html() and other log_*()

On Fri, 1 May 2020 at 13:10, Michael Orlitzky wrote: > > On 5/1/20 3:54 AM, John Cremona wrote: > > I agree with David. I use grep 1000 times a day and I do know how to > > use a computer (and do not appreciate being patronised) > > I'm poking fun at the reasoning behind adding these functions to

Re: [sage-devel] remove log_html() and other log_*()

I agree with David. I use grep 1000 times a day and I do know how to use a > computer (and do not appreciate being patronised), but I also use > serach_src() in the middle of Sage sessions a lot and tha seems much more > useful to me than switching to a different window and navigating to >

Re: [sage-devel] remove log_html() and other log_*()

On 5/1/20 3:54 AM, John Cremona wrote: > I agree with David.  I use grep 1000 times a day and I do know how to > use a computer (and do not appreciate being patronised) I'm poking fun at the reasoning behind adding these functions to sage, not the people who use them. I've been on the wrong side o

Re: [sage-devel] remove log_html() and other log_*()

On Fri, May 1, 2020 at 8:54 AM John Cremona wrote: > > I agree with David. I use grep 1000 times a day and I do know how to use a > computer (and do not appreciate being patronised), but I also use > serach_src() in the middle of Sage sessions a lot and tha seems much more > useful to me than

Re: [sage-devel] Re: Unable to build ecl-16.1.2.p5 on Ubuntu 20.04 LTS

On Fri, May 1, 2020 at 8:34 AM Andrew Bernard wrote: > > Ah, not so fast. More testing revealed that if you remove the Ubuntu package > libffi-dev, or perhaps don't install it in the first place a full clean > compile results. > > That's good news. > > I would therefore say that Ubuntu 20.04 LTS

Re: [sage-devel] remove log_html() and other log_*()

I agree with David. I use grep 1000 times a day and I do know how to use a computer (and do not appreciate being patronised), but I also use serach_src() in the middle of Sage sessions a lot and tha seems much more useful to me than switching to a different window and navigating to wherever my

[sage-devel] Re: Unable to build ecl-16.1.2.p5 on Ubuntu 20.04 LTS

Ah, not so fast. More testing revealed that if you remove the Ubuntu package libffi-dev, or perhaps don't install it in the first place a full clean compile results. That's good news. I would therefore say that Ubuntu 20.04 LTS is a viable platform. This was built from the sage-9.0 source tar