On 10/20/20 12:12 AM, Nathan Dunfield wrote:
-1: I don't really care what RealField.__repr__ returns, but cast a token no vote to object to the logical next move of breaking backwards compatibility by changing the meaning of RealField and/or RR. I see the need for a "genuine real field", but it seems a lot simpler just to call it something other than "RealField" and so not break a lot of existing users' Sage code.
Breaking user code is annoying, but in this case the fix is pretty trivial. You wouldn't have to read through the API documentation or anything -- just run find & replace on a few text files.
Having both a Real Field and a RealField and having them be two completely different things (one of which is not even a field!) would be far worse IMO.
-- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/f043b40e-d48d-96c4-2cbb-31e1f19211c1%40orlitzky.com.
