>
> I hope that too. Chris, is it ready for review?
>
1778 is on the docket waiting right now. All the other commits have
been squashed together and the whole thing passes all tests.
Part of he question is how fine you want the commit history to be.
This all started with trying to get rid of incorrect behavior of
expressions involving powers. Those changes influence a lot of core
needing simultaneous change so there is bound to be a large commit
that comes out of the work.
I also worked on the expansion routine, using a hint manager. This got
a partial review, some negative feedback because of timing issues, and
then it stalled. I think the benefits outweigh the slight slow-down:
o there is now partial keyword matching (eq.expand(c=1) will do
complex expansion),
o ordered hinting (eq.expand(mul_c=1) will do mul first and then
complex while
eq.expand(c_mul) will do them in reverse order.
So I need someone to make a decision whether this is a good direction
to go. I also changed how expand does deep processing. I think that
Ben's results indicate that this is a step in the right direction. I
would prefer to keep both mods together for expand, but I think I can
redo the deep processing and lose the hint manager.
There are a lot of other changes, too. I'll keep pulling out the
smaller issues and posting them for review. Any of the code that is in
'1766 et al' (the squashed history) can be viewed and commented on,
but I think people don't want to do this so I'll pull out the commits
for review.
--
You received this message because you are subscribed to the Google Groups
"sympy" 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?hl=en.
