Comment #8 on issue 3560 by [email protected]: solve() is a giant mess
http://code.google.com/p/sympy/issues/detail?id=3560
Some comments:
- We *have* a Set class. And it already had things like Integers, Interval,
and TransformationSet (allows set builder notation).
- In general you can't use attribute access to get at solutions. One,
Symbols can have names that aren't valid Python identifiers. Two, symbols
are identified by their name and assumption, not just their name, so you
can have two different symbols with the same name. This can also happen
with different classes, like Wild or Dummy. Third, we have support for
solving for non-Symbols, like functions. So you have to use dictionary
style syntax to get this.
- Maybe you want solve(x**2 + y**2 < 1) to return the Set object
corresponding to a Disk (for now it would have to just be
TransformationSet((x, y), x**2 + y**2 < 1)). This seems to be a rather
loose definition of solving.
- A use for guessing (that well need to consider) is that you can reduce an
under-determined system. In this case, you need to know what variables it
picked.
But I get your point, though, which is that there's little more that we
might want from Sets than the variable solved for, except I guess for
syntactic sugar to maintain old APIs.
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy-issues?hl=en.
