No, I meant one that you were describing. There would be somewhere in the core that hasif NEW_ASSUMPTIONS make is_foo and Symbol(foo=True) call the new assumptions else: do what we are doing now This actually is only necessary if the new assumptions are really problematic. We should try just doing it, and running the tests, and seeing what happens. If it's a lot of work, then we can add the flag so that you can push it into master and fix the issues with pull requests. Then, once all the issues are fixed, we remove the flag (and all the old assumptions). This whole process should happen entirely in the development repo between releases. I guess changing other code to work simultaneously with both old and new assumptions is not easy, so we should either fix everything at once, or put similar wrappers in the code there too. The only purpose of the flag is to allow us to fix the issues in pieces without the work getting stale in a pull request. If there aren't that many issues, we shouldn't even do it. At the end, it will be easy to remove the old assumptions by just removing all the "else" clauses throughout the code base.
This is precisely my idea (though I suspect that there will be rather many issues, hence why I proposed the flag).
I will check (or at least try to estimate) how many issues there really are. -- 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?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
