> > I'm not sure if the input_set API is as friendly as it could be. Most > users are going to want to just toss in relations with the rest of the > equations, especially if they can be expressed using the assumptions > or using inequalities, like > > solve([sin(x) - 1, x > 0]) > > or > > solve([x**2 + y**2 - z**2, Q.integer(x), Q.integer(y), Q.integer(z)]) > > Maybe we should just make the API like this. If you want to represent > a complicated set, you can input some kind of Contains object (does > this exist yet?). That would also make it clearer what variables > correspond to what axes in higher dimensional sets. >
I agree that input_set API is not very friendly but it is consistent for both simple and complicated cases. I feel that the other methods will get complicated quickly as we try to increase the complexity of the input cases and will add to the maintenance overheads. As far as using relations are concerned good conversion tools to set and sufficient examples in documentation shall do as an alternative. solve(sin(x), x, input_set=(x>0).as_set()) For We will have reals as the default parameter for input_set as real so for simple cases user won't have to care about it anyway. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CADN8iuoqBJui_2L_rQiye5%3D3txzF-3k_zhSW7n-0K_gEYy8LDg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
