Sorry for the late reply. Thanks.
Why do you put rpyc_classic & other scripts in the scripts directory, instead of in the site-packages directory for rpyc? The other python packages that I've used install themselves this way. It makes much better sense to have all files for a given package in the package directory of the same name. This way the users only have to look one place to find the files for that package. On Sat, Nov 12, 2011 at 2:46 AM, Tomer Filiba <[email protected]> wrote: > tony, i'm CCing the mailing list as well. > please don't send me personal emails concerning rpyc. > > first of all, about the tutorial, you can open an issue on github and i > will get to that. > > about not being able to run rpyc_classic.py, please open a dosbox, cd to > the correct path, and run "python rpyc_classic.py". > this should give you the traceback, or indicate that python in not on your > system path, etc. > > > ----------------------------------------------------------------- > > *Tomer Filiba* > tomerfiliba.com <http://www.facebook.com/tomerfiliba> > <http://il.linkedin.com/in/tomerfiliba> > > > > On Sat, Nov 12, 2011 at 09:09, Tony Cappellini <[email protected]>wrote: > >> >> >> Hello Tomer, >> >> >> I'm on the new site, but it still references the old directory >> structures, and files which no longer exist. >> http://rpyc.sourceforge.net/tutorial/tut1.html >> >> I have rpyc3.1 installed, but there is no rpyc_classic.py on my system, >> as indicated in the link above. >> >> At the moment, I cannot get the classic server running on Windows XP with >> Python 2.7 installed. >> When I run classic.py, nothing happens. No errors are displayed. >> >> >
