So I have fixed all of the priority issues. I just need people to finish reviewing them (they are the pull requests at https://github.com/sympy/sympy/pulls/asmeurer that do not already have a "+1" in the comments). I haven't pushed anything in yet because I plan on doing it in one fell swoop after everything is reviewed to make it simpler.
But there is one final issue blocking the release, which is Issue 1376 (sympy.sum overrides built-in sum with a different call syntax). The reason I haven't fixed this one is that we need to make a decision about what to do with sum(). The problem is that we are overriding the Python builtin sum() with our own sum() that has a different calling syntax. Proposed solutions are: 1. Make our sum() act like Python's sum() when given a list. Mateusz has implemented this in his poly12 branch, but some people don't like it. 2. Rename our sum. Suggestions so far have been sum_() and summation(). 3. Just use Sum().doit(). This is the only suggest that I do not like, because it makes it look like Sum doesn't work if people don't know about doit(). 4. Keep overriding sum() and mention it in our docs. I am fine with any of these (except I really don't like 3), but we need to come to an agreement so that we can merge in polys12 and get the release out. Aaron Meurer On Jan 3, 2011, at 6:50 PM, Aaron S. Meurer wrote: > I would like to get SymPy 0.7.0 released before my classes start again in a > few weeks. From what I see, these are the things we need to do before > releasing: > > - Merge in Mateusz's polys branch. See issue 2133. Mateusz and I are > currently working on getting this into a mergable state, and I think we > should be able to get it in very soon. > > - Update mpmath. See http://code.google.com/p/sympy/wiki/UpdateMpmath for a > guide on how to do this. > > - Fix all the critical priority issues > (http://code.google.com/p/sympy/issues/list?can=2&q=Priority%3DCritical), or > lower their priority. These are the failing doctests in Python 2.6.6 (2041), > Vinzent's ghost test failures (2110), and an improvement to the doctester to > catch tests that aren't being caught (2126). > > - There is a test failure in Python 2.4 right now because of an unimported > all/any somewhere that we need to fix. > > Those are the things I think we *have* to do before releasing. But we also > should try to do the following. > > - Close NeedsReview issues > (http://code.google.com/p/sympy/issues/list?q=label:NeedsReview), or postpone > them until after the release. > > - Close Milestone-Release0.7.0 issues, or postpone them: > http://code.google.com/p/sympy/issues/list?can=2&q=Milestone%3DRelease0.7.0. > > - Close all open pull requests, or postpone them. > https://github.com/sympy/sympy/pulls. > > So if people can help with any or all of these, that would be much > appreciated. In particular, if someone has a fix for the doctest failures, > that would be very good. Also, Vinzent, I think you are still the only one > who can reproduce your ghost test failures, so either you will have to do > something about that, or we will have to postpone/close as invalid the issue. > > > Also, one thing that I cannot do is review my own branches > (https://github.com/sympy/sympy/pulls/asmeurer), so if people could do that, > that is would be great too. > > Aaron Meurer -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sy...@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
