Well, the deadline has past, so you can no longer edit the application in Melange. However, if you can still add comments to it, which we will see.
Don't worry, we will not grade proposals based on when they are submitted (they're either in by the deadline or they're not) :) Aaron Meurer On Apr 8, 2011, at 9:02 AM, VPeric wrote: > Unfortunately, I didn't have time before today to write my > application. It can now be found here: (and the same on melange) > > https://github.com/sympy/sympy/wiki/GSoC-2011-Application:-Vladimir-Peri%C4%87:-Porting-to-Python-3 > > I apologize for dropping it at the last minute, but I would appreciate > any comments you might have, especially related to the schedule (how > realistic it is, or should it even be expanded). Thank you all in > advance, > > On Mar 24, 6:50 pm, Ronan Lamy <[email protected]> wrote: >> Le jeudi 24 mars 2011 à 10:36 -0600, Aaron S. Meurer a écrit : >> >> >> >>> On Mar 24, 2011, at 6:07 AM, VPeric wrote: >> >>>> On Mar 23, 8:30 pm, Mateusz Paprocki <[email protected]> wrote: >>>>> Hi, >> >>>>> It's a good question whether this is "big enough". Surely it's important >>>>> enough to consider this as a GSoC project. I think that the biggest >>>>> problem >>>>> currently (unless I forgot about something else) are __cmp__ methods. We >>>>> are >>>>> gradually taking care of this issue across SymPy but there is still a lot >>>>> of >>>>> work to be done in this area. It's up to you to recognize issues that have >>>>> to be fixed and figure out a schedule you would like to follow (don't >>>>> hesitate to ask, because we already made some effort to make SymPy >>>>> compatible with Python 3 and we have some code in development branches >>>>> that >>>>> could help you). If it happens that there is not enough work in porting >>>>> SymPy to Python 3, then you might consider widening the project and make >>>>> SymPy run in a subset of Jython, PyPy, IronPython, etc. (I don't remember >>>>> which are already supported). >> >>>> To be completely honest, I haven't ported such a big project before so >>>> I fear I won't be able to accurately judge how long each part is going >>>> to take. So, any help in that regard is quite appreciated. I tried to >>>> look at the work done previously, but the links were dead. >> >>> I think the main thing was fixing the __hash__ warnings. These turned >>> out to not be as bad as we thought they would be due to a bug in >>> Python (the moral is use -3 in Python 2.7, not Python 2.6). See >>> commit 53bf7024b466c5076aa6a12d3d4dc3532533af58. Also, some headway >> >> Yes, except that those hashes are wrong. We only silenced the >> warnings/py3k errors, but we can still have a == b but hash(a) != >> hash(b). It'll come back to bite us at some point (anyway, this is as >> much a bug in Python 2 as in Python 3, so quite tangential to Vladimir's >> project). > > -- > 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. > -- 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.
