Thanks Ralf!
--
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
On Monday, June 13, 2016 at 12:28:11 AM UTC+2, Paul Masson wrote:
>
> 1) How a function is made symbolic as opposed to a Python callable
>
Builtin functions are callable classes deriving from
Function, see symbolic/function.pyx They are created
on start up. Most symbolic objects have a C++
Thanks for getting this fixed so quickly.
As a followup question, is there documentation somewhere that provides an
overview of program flow in the labyrinth that is SageMath? More
specifically I'd like to understand
1) How a function is made symbolic as opposed to a Python callable
2) The
8-year old bug, triggered by recent Pynac changes
http://trac.sagemath.org/ticket/20818
Please review.
On Sunday, June 12, 2016 at 12:57:39 PM UTC+2, Volker Braun wrote:
>
> Its probably this:
>
> sage: arcsinh(float(0.1))
> 0.09983407889920758
>
> sage: arccsch(float(0.1))
>
Its probably this:
sage: arcsinh(float(0.1))
0.09983407889920758
sage: arccsch(float(0.1))
(2.99822295029797+0j)
On Sunday, June 12, 2016 at 7:50:34 AM UTC+2, Ralf Stephan wrote:
>
> On Sunday, June 12, 2016 at 3:07:07 AM UTC+2, kcrisman wrote:
>>
>> There may have been some change in Pynac
On Sunday, June 12, 2016 at 3:07:07 AM UTC+2, kcrisman wrote:
>
> There may have been some change in Pynac that leads it to return complex
> values more often now?
>
I have no idea abot plot(). How to determine which values are offending?
--
You received this message because you are subscribed
There may have been some change in Pynac that leads it to return complex
values more often now?
On Saturday, June 11, 2016 at 6:43:42 PM UTC-4, Paul Masson wrote:
>
> Attempting a simple plot( arccsch(x),-1,1) leads to the error message
>
> verbose 0 (3531: plot.py, generate_plot_points)
