-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Should we remove old assumptions? #6738
Comments
Original comment: http://code.google.com/p/sympy/issues/detail?id=3639#c1 |
Referenced issues: #6730 |
The issue is, can we refactor the core (or really do anything with it) if it still has the old assumptions sitting around. Now, a phase out period could be argued. Original comment: http://code.google.com/p/sympy/issues/detail?id=3639#c3 |
It depends what sort of refactoring you have in mind. Having the old assumptions around is not a problem in itself, IMO. Original comment: http://code.google.com/p/sympy/issues/detail?id=3639#c4 |
It would be nice to remove some of the magic around Symbol. What will sympy use in general code? What will E.g.
Original comment: http://code.google.com/p/sympy/issues/detail?id=3639#c5 |
Yes, this a real problem that could be fixed quite easily today (by having the new assumptions call the old ones), were it not for the fact that there are incompatible definitions (cf. issue 5976 ). Referenced issues: #5976 |
rlamy says
I think it would be a serious mistake to throw away a working system (the old assumptions) for the sake of an untested one with known deficiencies (the new assumptions). It would probably be more productive to view the new assumptions as complementary to the old ones, and treat it as a given that they are intrinsically more powerful, but slower and more cumbersome to use than the old ones.
Original issue for #6738: http://code.google.com/p/sympy/issues/detail?id=3639
Original author: https://code.google.com/u/109882876523836932473/
The text was updated successfully, but these errors were encountered: