Re: [sage-devel] Is anybody using set_coercion_model()?

I was one of the original authors, and removing the possibility of additional models sounds fine to me. I agree that nobody's going to implement them at this point. David On Tue, Mar 14, 2017 at 5:26 AM, John Cremona wrote: > On 14 March 2017 at 12:10, Jeroen Demeyer

Re: [sage-devel] Is anybody using set_coercion_model()?

On 14 March 2017 at 12:10, Jeroen Demeyer wrote: > The coercion model in Sage seems to be designed to allow it to be changed: > there is a global object coercion_model defined in element.pyx which can be > get/set using get_coercion_model() and set_coercion_model(). So *in

[sage-devel] Is anybody using set_coercion_model()?

The coercion model in Sage seems to be designed to allow it to be changed: there is a global object coercion_model defined in element.pyx which can be get/set using get_coercion_model() and set_coercion_model(). So *in theory* it is possible to implement a different coercion model. However,