use factory.connect. classic is a simple wrapper that apparently doesn't expose that functionality
https://github.com/tomerfiliba/rpyc/blob/master/rpyc/utils/factory.py#L78 ----------------------------------------------------------------- *Tomer Filiba* tomerfiliba.com <http://www.facebook.com/tomerfiliba> <http://il.linkedin.com/in/tomerfiliba> On Thu, Aug 25, 2016 at 6:39 PM, Sagy Drucker <[email protected]> wrote: > which version of rpyc is that? > i'm using 3.3.0 and the *rpyc.classic.connect* method has no keyword > argument "*config*" > > > On Thursday, November 1, 2012 at 2:25:42 PM UTC+2, shay berman wrote: >> >> Hello >> >> I have a strange problem while running commands (popen via rpyc) on >> windows2012 server - I get exit code (11) on few commands that I am running >> (not consistent - some times the command is working ok and some times it >> return exit code 11). >> >> The output of the rpyc server is not telling me much. >> There is any why to run the rpyc server with higher log verbosity ? >> For example, not just to logging the welcome & accepted, to log also >> which object was asked to be run and what its status(+ date\time). >> >> thanks >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "rpyc" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "rpyc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
