Merge lp:~ipython-contrib/ipython/ipython-zmq into lp:ipython/0.11
Proposed by
Fernando Perez
Status: | Needs review |
---|---|
Proposed branch: | lp:~ipython-contrib/ipython/ipython-zmq |
Merge into: | lp:ipython/0.11 |
Diff against target: |
243 lines (+232/-0) 2 files modified
IPython/core/ipzmq.py (+174/-0) IPython/kernel/ipkernelzmq.py (+58/-0) |
To merge this branch: | bzr merge lp:~ipython-contrib/ipython/ipython-zmq |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Fernando Perez | Disapprove | ||
Review via email: mp+24087@code.launchpad.net |
Description of the change
Google Summer of Code branch proposal for the zmq port.
To post a comment you must log in.
Unmerged revisions
- 1242. By Omar Andres Zapata Mesa <omazapa@tuxhome>
-
-> Corrections in namespacing, using pep8 instead camel case.
-> Implemented send and recieve in ipzmq but it have some errors
-> I started to write ipkernelzmq but it is not functional yet. - 1241. By Omar Andres Zapata Mesa <omazapa@tuxhome>
-
Writing send and receive methods
- 1240. By Omar Andres Zapata Mesa <omazapa@tuxhome>
-
implementing the server and client in zmq, this module
init sockets to zmq conecction and let comunication between client and server.
º
I merged revisions 1237-1239 and cleaned the text up a little bit, but I did NOT merge 1240-41. The code in there will require further review, and we're now doing the move to github.
So once you start working on github, just remember to add the ipzmq.py file back to your git branch. But that code will need some fixes, which I can tell you about right away so you can start working on them:
- you are using 8 spaces, PEP 8 uses 4
- you are using camelCase, PEP 8 discourages that. Please read PEP 8 and adhere to it.
- do not use self.__X attributes with double underscore, they cause lots of problems in the long run. They are a mis-feature of python and should only be used in rare instances.
- Why aren't you using the code from the pyzmq examples as a starting point? That code already had much of what you are implementing here working...
So in summary: your docs have been merged (after fixing for capitalization and formatting, next time please be careful with that). The code isn't ready for merging.