[IPython-dev] Ipython frontend for two process
Omar Andrés Zapata Mesa
andresete.chaos at gmail.com
Sun Apr 3 23:09:30 EDT 2011
Hi all.
I am having a wierd problem with tab completion.
Description:
with the completer added to ipython's master repo
https://github.com/ipython/ipython/blob/master/IPython/zmq/completer.py I
have timing problems because it dont use complete_request's messages in the
new model, then I create my own completer and it is very simple
https://github.com/omazapa/ipython/blob/frontend-logging/IPython/frontend/terminal/completer.py
using
new methods and messages.
Note that the line 45 have commented #print self.matches it is for debug the
return's list, the print show that the content is good. In a normal case
readline get the list matches and print it in stdout, but it is not working.
Some idea?
2011/4/3 Omar Andrés Zapata Mesa <andresete.chaos at gmail.com>
> Hi Fernando.
>
> Ok I am studing the qt code and the new link. I hope have some result
> tomorrow.
>
> PD: I have ready raw_input code too.
>
> Thanks
>
> On Sun, Apr 3, 2011 at 3:22 PM, Fernando Perez <fperez.net at gmail.com>wrote:
>
>> Hey Omar,
>>
>> 2011/3/29 Thomas Kluyver <takowl at gmail.com>:
>> > Thanks, that's working now. As for tab completion, if you look in
>> > IPython/core/completer.py, at line 865, uncomment the DEBUG = True line,
>> and
>> > it should give you more info on what's going wrong.
>>
>> This looks like a great start, thanks! As Thomas mentions, that's the
>> easiest way to activate debugging for tab completion. What I
>> recommend is that you study the qt frontend for behavior, since
>> effectively what you are doing is implementing the same basic
>> architecture. The qt console converts a tab key event into a
>> completion call to the kernel, in your case you'll need to do that via
>> readline by registering a completer.
>>
>> I've put up the original zmq example as its own repo here:
>>
>> https://github.com/fpereadlinerez/zmq-pykernel<https://github.com/fperez/zmq-pykernel>
>>
>>
>> so that you can easily see how all that works. This is the old code
>> you may have already seen, but having it available in an
>> easy-to-reference permanent location is probably a good idea.
>>
>> Let us know if any of this doesn't make sense...
>>
>> Cheers,
>>
>> f
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20110403/a9936b37/attachment.html>
More information about the IPython-dev
mailing list