What do I have to do to set up python 2.3 to run centrally on a Win 2000
network instead of installing it on every workstation? Is it possible?
How do I go about updating individual registeries? I'd appreciate some
pointers and advice if any one can help.
Well, if you have a Windows network, you need scripted installs :-P
Otherwise administering a Windows network is too much of a PITA in my
> Is it possible?
Sure. Get an installed Python, copy the c:\python23 directory to a
network share, then grab the file %SYSTEMROOT%\system32\python23.dll and
copy it alongside python.exe. Now all your clients can access Python via
the share name.
> How do I go about updating individual registeries? I'd appreciate some
> pointers and advice if any one can help.
Python itself doesn't need any registry entries. If you use the COM
stuff of the win32 extensions, though, this might be different.
One can get by without registry entries even there, with a little
trickery. I've posted an example of such trickery a few weeks
ago in the newsgroup... untested on 2K however, but working on
networked Win98 machines and likely to work on 2K/XP as well.
Can you check whether "import pythoncom" and "import pywintypes"
and (if you've installed the Win32 extensions) "import win32api"
If these work without your having to do anything to the registry,
I'm curious about the installation process you used, since we
had to do additional steps to get the same result.
You are aware that recently Mark changed things so the the registry is
no longer used for importing?
No! Thank you... my experience comes from setting this up with
versions prior to the latest (or "recently" released ones) so
likely once we upgrade we can abandon the trickery. Good to know.