On Thu, Jun 13, 2013 at 12:45 PM, kcrisman <kcris...@gmail.com> wrote: > >> Smells like a bug... > > > Not exactly. The documentation for solve makes it clear (I hope!) in the > examples that these are "generic" variables generated by Maxima which we do > not make "Sage" variables. They just mean, "any old integer" (hence 'z').
The documentation under 'solve?' doesn't have this, but it's there in the manual. Could you guys add a bit to the manual where you show the method for coercing the dummy z variable into a proper sage variable please? Sorry to keep on here, but I've got three other related queries: (1) "solve?" gives me " solve(sin(x)==x,x,explicit_solutions=True)" as an example which returns an empty list of solutions. But x=0 surely counts as an explicit solution? I guess my interpretation of an empty list as "there cannot possibly be any solutions of this form" can't be right. Can we add a legal disclaimer along the lines of "an empty list does not guarantee the absence of solutions"? (2) Trying "solve(sin(x)==x,x,to_poly_solve=True)" gives me an unhelpful error message about indexing. What does this message mean and how can I mitigate it? (3) The docs say "For more details about solving a single equation, see the documentation for the single-expression solve()" Where can I find this documentation online? -- Robin Hankin Uncertainty Analyst hankin.ro...@gmail.com -- 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 post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
