Since it looks like you had a Sage cell instance do this, you should be 
able to link to the code even, using the "Share" button on Sage cell 
server.  Thanks, that will help our team!

On Saturday, January 18, 2020 at 11:55:29 AM UTC-5, Nils Bruin wrote:
>
> On Saturday, January 18, 2020 at 7:19:03 AM UTC-8, mendes wrote:
>>
>>
>> RuntimeError: Encountered operator mismatch in sr-to-maxima translation
>>
>>
> The error indicates that the sage-to-maxima dictionary used in sr_to_max 
> is in an inconsistent state. Its state is a mix of preinitialization and 
> caching translations as it goes along, so inconsistent state indicates 
> there's a fragile initialization somewhere. the py2/py3 switch has all 
> kinds of small effects, so it could change the enumeration order of a set 
> somewhere, so that the initialization happened to go right in py2 but now 
> ends up going wrong in py3.
>
> Concerning your hint of a bug:
>
> integrate(unit_step(x),x,-1,1)
>
> works just fine for me (it leaves the integral unevaluated). Without a 
> piece of code that reliably reproduces the error you encounter it's 
> virtually impossible to find what's wrong.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/3fe8d66f-c3bf-4d1e-9e02-41584d1916a8%40googlegroups.com.

Reply via email to