runciter: well, yeah I was looking for a python interpreter to support some terminal shortcuts that make his usage more useful, but... I don't think that the server can be able to send something while I'm in an interpreter
runciter
it can
rememberYou
really?
Oh, awesome
because in the past, I just used a ClientFactory that creates an instance of a Protocol, worked fine except that I had a poor terminal
so when you said that I don't want to use any manhole it's inside the server file, right?
runciter
rememberYou, the problem is that the pieces you need from conch aren't easily reusable
goldfish joined the channel
rememberYou
yeah, and I don't understand why no more documentation about this with examples, could be useful. I also saw that I wasn't the only person to found it complex (https://stackoverflow.com/questions/13871738/ho...)
terrycojones joined the channel
runciter
rememberYou, documentation takes time and effort to write, and both of those are in short supply
rememberYou
I think create an little tutorial about this later when I will be able to achieve that, could help a lot of people that are in trouble with that because use a terminal without any readline functionality it's a pain
runciter: I will probably do a pull request about that when I will well understand what I'm doing because I'm still in trouble. Just to know, the client doesn't need anymore code right?
I mean... the python interpreter already do all the stuff, all I need to do it's to thinking it out how display back output of the API from the server to the client without use manhole because it will create another python interpreter to the server, if I well understood :)
I though use `dataReceived` from Protocol in the server and check if the data came from the client or the API and according it just use `transport.write(...)`