On Jun 21, 2010, at 4:27 PM, James Pearson wrote: > On Mon, Jun 21, 2010 at 12:36 PM, Ondrej Certik <[email protected]> wrote: > We need to find someone who would take a lead on this and start > pushing things in. > > Would you have time to do it? > > Possibly. I just started work again after the quarter-end and a week off, > and it's looking like I will be working only half- to 3/4-time, which, with > the lack of any summer classes, provides me with plenty of time for > interesting projects. > > There are a few important considerations, however. First, I have a number of > (personal) projects I promised myself to get some work done on. They are > mostly small little things, and I've made great progress on the one I was > most concerned with, but nonetheless, they are there. Secondly, I am not > particularly familiar with the SymPy codebase; I used it a bit in a project a > while ago (which is how I ended up subscribed to this list), but other than > that and my occasional reading of these messages, I am a complete newcomer, > both to SymPy and CAS like this. > > With those things said, I would be willing to spend some time working on the > issues that have been brought up, and in general, nag people about Py3k > issues and such, to make sure that development in that area continues (even > if at a slow pace).
Great! Even a little bit, like removing the problems brought up by -3 would be very helpful, and if we can get a full working port, that would be even better. If you have problems or questions concerning the codebase or other things, feel free to ask them here or on IRC (#sympy in freenode). Some parts of the code base are very well documented, but unfortunately, others are not. Speaking of Python 3, do you know how to fix the Overriding __cmp__ blocks inheritance of __hash__ in 3.x and Overriding __eq__ blocks inheritance of __hash__ in 3.x problems? These, other than the use of cmp functions in sort(), seem to provide the most challenge of the warnings given by -3. Also, I should note that the warnings issued by -3 and the things that 2to3.py fixes are not disjoint. -3 only warns about things that can already be fixed in Python 2.6. 2to3.py fixes things that can be fixed algorithmically. For example, tuple parameters will both appear in -3 warning and can be fixed by 2to3. I don't know if there are any major things that would appear in neither: things that cannot be fixed in Python 2.6 and also cannot be algorithmically fixed. If there are, they would present a problem. Just some advice. Aaron Meurer -- 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.
