Re: RMI with Pyro et al
Irmen de Jong schrieb: > Diez B. Roggisch wrote: > >> Go install cygwin (but not it's included python-interpreter, or at least >> make sure you have your python path properly under control) and then >> simply >> start the script from the command-line. And hit C-c if you need it to >> stop, >> and restart it. Only start it as service if it's deployed. > > What's cygwin got to do with it? Being the better shell. Nothing else :) Diez -- http://mail.python.org/mailman/listinfo/python-list
Re: RMI with Pyro et al
Diez B. Roggisch wrote: > Go install cygwin (but not it's included python-interpreter, or at least > make sure you have your python path properly under control) and then simply > start the script from the command-line. And hit C-c if you need it to stop, > and restart it. Only start it as service if it's deployed. What's cygwin got to do with it? -irmen -- http://mail.python.org/mailman/listinfo/python-list
Re: RMI with Pyro et al
Sells, Fred wrote: > Diez B. Roggisch wrote > . Why do you want that (hot deploy) >> anyway? Does startuptime of a script really bother you? >> shouldn't take >> more than a few seconds. > > My primary need is development/debug. I'm a Pyro newbie and I add a > feature and then test. The only way I've found to kill the Pyro server > on XP is to open the task manager and kill the python task (hopefully > the right one). > > > How do you start "the pyro server"? Are you talking about the Windows Services that you can simply start/stop with: net start PyroNS net start PyroES net stop PyroNS net stop PyroES ?? Often it is way simpler to just use the pyro-ns.cmd / pyro-es.cmd batch files and stop the server with a simple ^C in the console window. -irmen -- http://mail.python.org/mailman/listinfo/python-list
RE: RMI with Pyro et al -- thanks for help
thanks, that should do it Diez wrote: > Go install cygwin (but not it's included python-interpreter, > or at least > make sure you have your python path properly under control) > and then simply > start the script from the command-line. And hit C-c if you > need it to stop, > and restart it. Only start it as service if it's deployed. > > Diez > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
RE: RMI with Pyro et al
Sells, Fred wrote: > Diez B. Roggisch wrote > . Why do you want that (hot deploy) >> anyway? Does startuptime of a script really bother you? >> shouldn't take >> more than a few seconds. > > My primary need is development/debug. I'm a Pyro newbie and I add a > feature and then test. The only way I've found to kill the Pyro server > on XP is to open the task manager and kill the python task (hopefully > the right one). Go install cygwin (but not it's included python-interpreter, or at least make sure you have your python path properly under control) and then simply start the script from the command-line. And hit C-c if you need it to stop, and restart it. Only start it as service if it's deployed. Diez -- http://mail.python.org/mailman/listinfo/python-list
RE: RMI with Pyro et al
Diez B. Roggisch wrote . Why do you want that (hot deploy) > anyway? Does startuptime of a script really bother you? > shouldn't take > more than a few seconds. My primary need is development/debug. I'm a Pyro newbie and I add a feature and then test. The only way I've found to kill the Pyro server on XP is to open the task manager and kill the python task (hopefully the right one). -- http://mail.python.org/mailman/listinfo/python-list
Re: RMI with Pyro et al
Sells, Fred schrieb: > I need a simple client/server architecture with clients on linux and servers > on windows. There is no UI in this part, just business rules and access > control. > > Pyro seems pretty cool for this due to it's simplicity. I'm just starting > with it and have not been able to get the server side to "see" changes to a > module. The only way I can stop the server is with the Task Manager. Can > anyone offer some insight into > 1. stopping/starting the server - perhaps as a windows service. > 2. getting the server to recognize new modules "on the fly", i.e. when the > .py file is changed. That can be done, but isn't supported out-of-the-box. Essentially, you have to create a watch-thread that checks timestamps on python-files and then restarts some service if some change. However, it might be difficult to make that play nicely with pyro - after all, it stores some state, reloading stuff makes that go away. So - I wouldn't advice to really implement that. Why do you want that anyway? Does startuptime of a script really bother you? shouldn't take more than a few seconds. Diez -- http://mail.python.org/mailman/listinfo/python-list
