One of the things I like about Python is that
* it doesn't actually need an installation. *
It is sufficient to set up PATH (and, if you like, PYTHONPATH)
accordingly to start python. However, you need the DLLs somewhere
in the Python directory, too.
That way it is possible to install Python applications in a minimal-invasive
fashion: Just copy one directory to the hard-disk (or a network drive) and
create a shortcut to some start-app.cmd script
For example, this is a great advantage if you need to install a Python
application
on a client's application server,
since the client's IT departments in reponsibility for the server
absolutely don't like it when programs modify PATH or install DLLs in the
%WINDIR%\System32 directory - and they are right here!!!
Think of what happens if a program modifies PATH: The modification does not
affect running services, of course. But *after a reboot* (possibly a few
months later),
the old services will find another version of some program than before, and
then
someting is going to crash!
I have seen too much trouble of this kind after the installation of a
different Perl
version or a another Oracle product. The reason is then quite hard to find:
if the
installation of another software was 3 months ago, will anyone remember? And
will anyone even consider it could be the reason for the fault after the
reboot?
Well - I will, but most others probably won't.
I don't want this kind of trouble too happen with Python!
So, please try keeping the Python installation as minimal invasive as
possible.
Note: This could also be an option for the installation.
Henning
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
