----- Original Message ----- From: Ronald G Minnich <[EMAIL PROTECTED]> To: Jan Kok <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, January 07, 2002 10:11 AM Subject: Re: New NLBConfig
> > I have installed and committed Jan's new NLBConfig. I have committed it as > NLBConfig (no .py) so the old and new are still there. I hope that some of > you out there can test this new improved tool. I forgot to mention, NLBConfig should be exectuable. Does CVS support having files set executable when you check them out (as RCS and other version control systems do)? If not, the user will have to "chmod +x NLBConfig" after downloading. The Makefile action for rebuilding the Makefile et al also assumes that NLBConfig is executable. > Jan, a question on naming. All the python executables on my machines have .py > suffix, e.g. > /usr/lib/python1.5/macpath.py I guess it has to do with how modules are found, for example import Sound.Effects.echo loads the file .../Sound/Effects/echo.py (see the documentation for the import statement). I can't type mail and play with python at the same time, but I think you can have a script "foo" and just do "python foo" to run it. I don't know if you had a script "bar.py" and you said "python bar", would python look for bar.py if it couldn't find bar? > So why not have NLBConfig.py? Just wondering. No deep, subtle reasons, I just wanted to simplify the way it was called, "NLBConfig ..." instead of "python NLBConfig.py ..." But that requires that the script be set executable... :-) Cheers, - Jan > Also we will do the rename of the tool at some point ... > > thanks > > ron >
