Hi Ed, As Carlos mentioned, the v2.1.14 development version should be compatible with at least Python 3.3: http://spyder-ide.blogspot.fr/2013/01/spyder-v2114-supports-python-3.html
Python 3.0-3.2 compatibility is still in an early stage of development (I still haven't got the time to test it): https://code.google.com/p/spyderlib/issues/detail?id=944 https://code.google.com/p/spyderlib/issues/detail?id=1243 I've experimented a migration procedure on different projects: guidata, guiqwt and winpython (and also formlayout). So far, it has proven to be quite successful for implementing single code base compatible with both Python 2.6-2.7 and Python 3.3. The different steps may be seen in the Mercurial changesets named with the "Python 3 compatibility" prefix. I'm still waiting for v2.2 to be released before applying those changes on the v22 branch. In the meantime, compatibility issues with Python 3.0-3.2 still need to be addressed in the v21 repository. Right now, that would be the next thing to do. Cheers, -Pierre 2013/3/5 Carlos Córdoba <[email protected]>: > Hi Ed, > > Thanks for your kind words. We've worked really hard to let our users get > the most of IPython without configuring anything with text files or magics. > > There has been a lot work to port Spyder to Python 3, but not in our 2.2 > repo but in our 2.1 one. I know it sounds strange, but 2.2 was about to be > released and we didn't want to delay it until Python 3 support was added. > > So Pierre, our lead developer, took our 2.1 repo and started to port it to > see how hard it could be. You can download it with mercurial from here: > > http://code.google.com/p/spyderlib/source/checkout?repo=v21 > > and test it with 3.2 or 3.3. Pierre took the u(...) approach and I think > added future imports everywhere. Try to use it and tell us how things work > for you. After 2.2 is released, that work would be the base to port the new > code base for 2.3. > > Cheers, > Carlos > > El 28/02/13 05:44, Ed Schofield escribió: > >> Hi everyone, >> >> I'm very impressed with Spyder, especially the new IPython Qt console >> integration. Thanks for all your hard work. The latest release is great! It >> has come a long way even in the last couple of months. >> >> I'd like to help out with the Python 3.x port. Where would I start? Which >> is the right branch to work on? Has a decision made about whether to support >> only 3.3+ or to use the u(...) function everywhere for unicode/string >> compatibility? Is there a general plan of attack ... maybe something like >> first converting the codebase to using from __future__ imports everywhere? >> (print_function, division, absolute_import)? (I see that there's a >> smattering of these at the moment but it's not consistent.) Would you take >> the same approach as in the experimental 2.1.14 branch, or are there lessons >> you learned from this port that would spur you to do it differently next >> time? >> >> Best wishes, >> Ed >> -- >> You received this message because you are subscribed to the Google Groups >> "spyder" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/spyderlib?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "spyder" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/spyderlib?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
