Hello, I'm a student at the Faculty of Electrical Engineering, Czech Technical University in Prague. I'm studying Open Informatics, which is a study program orientated towards research and the utilization of new technologies.
While I have experience with several languages (notably C, Java, Prolog), Python is by far my favorite language. I find the issues related to conversion to Python 3 particularly interesting, and would like to work on porting SymPy to Python 3. The porting is inevitable if SymPy is to survive, and doing it sooner rather than later offers advantages that could be helpful in increased adoption (and hence increased development), so I consider it a very worthwhile pursuit. My main problem is whether this is simply "big enough" for a GSoC project? While it is listed on the Ideas page, after a cursory glance at the code I don't see any major problems here (or I simply missed them, of course). I have read about the last time such a conversion was attempted and the problems encountered, but as that was over 18 months ago, I believe most of those problems can be solved now. My plan would be to first run in 2.6 with no errors (ie. "Python -3"), which shouldn't be too difficult (around 150 errors, most of which look trivial), and then try to maintain a dual codebase with automatic running of the 2to3 tool when building for Python3 (which is the recommended procedure). Problems might arise from the fact that SymPy currently supports Python 2.4 or higher, but this would have to be solved as it comes up. I hope it will be possible to keep supporting 2.4, though limiting it to 2.6 would likely result in cleaner code. Thank you for your time, Vladimir Perić -- 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.
