New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Expression._convert a visible method #12577
Comments
comment:7
I wonder if, rather than just directly expose The problem with
where the last case is what you get if you tried to convert some arbitrary expression (like a polynomial, or solution to a DE) to "numerical". So yes, what we probably want here is something more like |
comment:8
I think it's useful in general to be able to change "back" from an approximate ring to an exact one. A trivial example:
But I agree that the user interface is key. The name "convert" is no good -- it's too general anyway but doesn't tell you what's being converted. Partially as a result of those two things, it's also not discoverable via tab-completion. The best altername name that I've been able to come up with so far is |
comment:9
|
comment:10
The problem with "change" also kind of problematic since it implies (to me anyways) an in-place modification, when really you're returning a new expression. Maybe |
comment:11
The benefit of
So, returning a copy is at least consistent. But aside from the nominal similarity to |
comment:12
Removing the "beginner" tag from old tickets. Some could be returned to beginner-friendly status by adding a comment about what needs to be done. Some others might be easy for an experienced developer to finish. Related ticket: #24850. |
It would be nice if the
_convert()
method of symbolic expressions were made visible (and possibly renamed, if "convert" is too general). This has come up in two or three times before, and I needed it long before I bothered to ask for help:http://groups.google.com/group/sage-support/browse_thread/thread/88e48ccbccfc56cd
http://groups.google.com/group/sage-support/browse_thread/thread/70e4c1eaaa632056
Component: symbolics
Issue created by migration from https://trac.sagemath.org/ticket/12577
The text was updated successfully, but these errors were encountered: