- Week 1: Simple client/server pyzmq module implemented from the previous work to the GUI needs.
- Week 2 and 3: Multiline input in a cell form that is sent to the kernel as a string, each cell has its own widget so they can be edited indepently.
- Week 4-5: Capture all output streams from kernel and properly format exceptions and errors. Display streams corresponding to other clients that may be connected to the same kernel in a separate widget so they don't confuse the user. This output will be asynchronous, so it should be handled in the GUI without blocking the user input widget.
- Week 6: Stdin support: only one frontend at a time can communicate with raw_input calls made by the kernel. API for frontends to grab stdin.
- Week 7: debugger support. IPython calls a modified pdb, which reads from stdin using raw_input. So once raw_input handling is ready, it becomes possible to redirect the pdb session from the kernel to the GUI.
- Week 8: Subprocess support (print output of 'ls' in gui, for example).
- Week 9: Tab completion and function tooltips (GUI popup with the function details). Must gracefully timeout and avoid trying if kernel is busy
- Week 10: padding for any slip in previous schedule.
Ipython Zmq Status - IPython currently has all the things proposed for GSoC and so many features that improved the functionality. The design was changed in a little features in ...
2 years ago