On Fri, Jan 28, 2011 at 10:34 PM, Christian Heimes
Am 28.01.2011 20:29, schrieb Raymond Hettinger:
At the very least, we should add some prominent instructions for getting the command line version up and running.
/me pops out of Guido's time machine and says: "execute Tools/scripts/win_add2path.py"
I'm -1 on adding Python to %PATH%. The private MSVCRT DLLs may lead to unexpected side effects and it doesn't scale at all.
Can you explain that part? There are no any MSVCRT DLLs in my Python26+ installation directories.
What about people with more than one Python installation? I suggest that we add a single user specific directory or a global directory to %PATH% for all installations. Then the Python installer or 3rd party modules can drop executables like python3.3.exe or plip-3.3.exe into this directory.
python33.exe, but user story about people with more than one Python installation is a different one.
A .bat file won't do good because .bat files must be called with "call python33.bat" from another .bat file or the first one gets terminated.
Wow. I've spent so many years in Windows console and didn't know that. Thanks.
We can even use a single and simple executable as template for all tasks:
* get registry key from resource section of the executable * use the registry key to lookup the location and name of pythonXX.dll * load DLL * get optional dotted module name for resource section * either fire up interpreter as shell, with **argv or -m dotted.module.name **argv
Done ;)
Actually, I would like to see the code that dynamically finds pythonXX.dll that is available on the system, and loads it into memory. This will be extremely useful for writing 3rd party application plugins in Python. Plugins that they only work when Python is installed and it doesn't really matter which Python version is there. But that is another story also. -- anatoly t.