Season of KDE is an outreach program hosted by the KDE community. This year I am working as a mentor to a long time requested project related with Cantor – the development of Python 3 backend. You can read more about Cantor in my blog (texts in English and Portuguese). So, let’s say welcome and good luck to Minh Ngo, the student behind this project!
Hi,
My name is Minh,
I’m BSc graduated student. I’m Vietnamese, but unlike other Vietnamese students spent most of my life in Ukraine. Currently, I’m preparing myself to the Master degree that will start in the next semester.
Open source is my free time hobby, so I would like to make something that is useful for the community. Previously, I was participated in the GSoC 2013 program and in several open source projects. Some of my personal projects is available on my github page https://github.com/Ignotus, not so popular like other cool projects, but several are used by other people and this fact makes me very happy 🙂 .
Cantor is one of opportunities to spend time to create an useful thing and win an exclusive KDE T-shirt :). I decided to start my contribution with the Python3 backend, because few months ago I studied several courses that are related with Machine Learning, so I was looking for a stable desktop backend for IPython. A notebook version IPython I do not entirely like and its qtconsole version doesn’t satisfy me in terms of functionality, therefore I decided to find some existent frontend for IPython that I can tune for myself. And the story with Cantor began after than 🙂
Happy hacking!
Hi Minh,
That is a good idea, but if you would consider a pointer, your ability would be so much more impactful if you would use your QT-Fu in improving TeXmacs (http://texmacs.org). Adding support for talking to IPython kernel is an obvious ways, but there are many others.
Hi Alvaro,
Unfortunately, I don’t use *e*macs as an editor :). Vim is more acceptable for my soul.
Great to see more work going on in Cantor.
I am unclear from the description: is the new cantor backend going to actually use IPython, or is it going to be another pure python implementation like the current python 2.x one?
There was a backend for Python 2, currently I just made a modification to make it work with Python 3, but I do not claim that my contribution will only consist of it.