> does anyone know how I can automate installation of the Windows Python
> distribution, using python1.5.1.msi ?
See
http://www.python.org/download/releases/2.5/
then follow the link "automated installation" to
http://www.python.org/download/releases/2.5/msi/#automated
> I want to be able to r
Hi!
> 1.5.1
Sure? 1.5.1?
For Python 2.5, look ActiveState. Their distrib have silent option.
--
@-salutations
Michel Claveau
--
http://mail.python.org/mailman/listinfo/python-list
does anyone know how I can automate installation of the Windows Python
distribution, using python1.5.1.msi ?
I want to be able to run the installation without user interaction, and
pass default parameters (instead of user entries), during the
installation process. This can be done with other .m
I finally gave up trying to install to c:\Python25 and went with the
install to C:\. However, I tried to install a module called pywin32
(Python for Windows Extensions) and after recognizing that the Python
installation was in C:\ and saying it would install to C:\LIB\SITE-
PACKAGES, it would then
Bjoern Schliessmann <[EMAIL PROTECTED]> wrote:
>
>The last app I saw that had problems with whitespace was Worms 2
>(1997). YMMV (and I'm interested in it).
If only. Even the very latest Microsoft WDK (Windows Driver Kit, formerly
known as the DDK) cannot successfully build drivers if the source
Fuzzyman wrote:
> However I did once use a machine where Python had been installed
> into 'c:\Program Files\Python24'. It caused no end of problems...
What, "it"? The machine or the folder? What kinds of problems?
Regards,
Björn
--
BOFH excuse #170:
popper unable to process jumbo kernel
--
On Oct 25, 6:36 pm, TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
> On Oct 24, 11:22 pm, Tim Roberts <[EMAIL PROTECTED]> wrote:
>
> > TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
>
> > >I am trying to install Python 2.5 on Windows XP. It installs into the
> > >root directory on C:\ instead of C:\Pyt
Wildemar Wildenburger wrote:
> Of course, but that would constitute "common practice".
Ah, okay. That was what I actually meant ;)
> "Best practice" in my book is the one that causes the least
> trouble, which names-with-whitespace clearly don't. Though by this
> day and age, I admit that progr
Bjoern Schliessmann wrote:
> Wildemar Wildenburger wrote:
>> Bjoern Schliessmann wrote:
>
>>> Which I don't understand (works best for me, and is best practice
>>> in Windows).
>>
>> Best practice? Says who?
>
> Ok, LOL. So, now you expect me to cite some official source? Despite
> the fact tha
Wildemar Wildenburger wrote:
> Bjoern Schliessmann wrote:
>> Which I don't understand (works best for me, and is best practice
>> in Windows).
>
> Best practice? Says who?
Ok, LOL. So, now you expect me to cite some official source? Despite
the fact that the vast majority of windows installers
Bjoern Schliessmann wrote:
> Dennis Lee Bieber wrote:
>> Besides preferring an install path that doesn't have spaces...
>
> Which I don't understand (works best for me, and is best practice in
> Windows).
>
Best practice? Says who?
/W
--
http://mail.python.org/mailman/listinfo/python-list
On Oct 25, 12:36 pm, TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
> On Oct 24, 11:22 pm, Tim Roberts <[EMAIL PROTECTED]> wrote:
>
> > TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
>
> > >I am trying to install Python 2.5 on Windows XP. It installs into the
> > >root directory on C:\ instead of C:\Py
On Oct 24, 11:22 pm, Tim Roberts <[EMAIL PROTECTED]> wrote:
> TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
>
> >I am trying to install Python 2.5 on Windows XP. It installs into the
> >root directory on C:\ instead of C:\Python25 which it shows by default
> >as what it plans to install to. Selectin
Dennis Lee Bieber wrote:
> Besides preferring an install path that doesn't have spaces...
Which I don't understand (works best for me, and is best practice in
Windows).
> On a proper XP (or later) system, one needs ADMIN privileges to
> install/modify the contents of %PROGRAMFILES%. Any user can
TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
>
>I am trying to install Python 2.5 on Windows XP. It installs into the
>root directory on C:\ instead of C:\Python25 which it shows by default
>as what it plans to install to. Selecting D:\Python25 on a previous
>iteration put the exe in D:\ and did no
On Oct 24, 7:27 am, Bjoern Schliessmann wrote:
> TheFlyingDutchman wrote:
> > I am trying to install Python 2.5 on Windows XP. It installs into
> > the root directory on C:\ instead of C:\Python25
>
> BTW, what exactly is behind the idea to install to c:\python25
> instead of %PROGRAMFILES%\python
TheFlyingDutchman wrote:
> I am trying to install Python 2.5 on Windows XP. It installs into
> the root directory on C:\ instead of C:\Python25
BTW, what exactly is behind the idea to install to c:\python25
instead of %PROGRAMFILES%\python25?
Regards,
Björn
--
BOFH excuse #339:
manager in t
With C:\Python25 already existing, I tried to install to C:
\Python25\Python25. It installed to C:\.
--
http://mail.python.org/mailman/listinfo/python-list
I manually created C:\Python25 the reran the install program. The
installation program noted that C:\Python25 existed and asked me if I
still wanted to install there. After I said yes it installed to C:\.
--
http://mail.python.org/mailman/listinfo/python-list
I am trying to install Python 2.5 on Windows XP. It installs into the
root directory on C:\ instead of C:\Python25 which it shows by default
as what it plans to install to. Selecting D:\Python25 on a previous
iteration put the exe in D:\ and did not create a Python25 directory.
On the most recent i
20 matches
Mail list logo
