Vincent Wehren wrote:
To check what I mentioned on comp.lang.python earlier, I ran the installer
again (with 2.4.1 still intact), selected the "Change Python 2.4.1c1" radio
button, clicked the "Finish" Button, clicked the "Advanced" button, clicked
the "Cancel" button, and clicked "Yes" to the ques
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Ok, so it's likely incomplete download.
Definitely.
It's a bit of a misfeature that the icon appears on the desktop before
the download is complete. But I'd say there's no real issue here,
besides my impatience/inattention.
--
KBK
__
Kurt B. Kaiser wrote:
Do you happen to remember the precise error message?
"This installation package could not be opened."
Ah, that you get if the file is already open. Do you run some shell
extension that might want to look into the MSI file, or virus scanners?
I also recall a KB article that th
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>> I downloaded the 2.4.1c1 installer to the desktop and clicked on it.
>> It complained that it couldn't access the installer.
>
> Do you happen to remember the precise error message?
"This installation package could not be opened."
>
>> I then clic
Martin,
This is somewhat of a corner case, but maybe worth investigating:
To check what I mentioned on comp.lang.python earlier, I ran the installer
again (with 2.4.1 still intact), selected the "Change Python 2.4.1c1" radio
button, clicked the "Finish" Button, clicked the "Advanced" button, clic
Kurt B. Kaiser wrote:
I had some strange experiences.
Weird indeed.
I downloaded the 2.4.1c1 installer to the desktop and clicked on it.
It complained that it couldn't access the installer.
Do you happen to remember the precise error message?
I then clicked on the 2.4.1b2 installer and that started
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> I'd like to encourage feedback on whether the Windows installer works
> for people. It replaces the VBScript part in the MSI package with native
> code, which ought to drop the dependency on VBScript, but might
> introduce new incompatibilities.
I h
Michael Chermside wrote:
I tried several stranger things, like installing over 2.4.0 but in a
different directory. Everything worked like clockwork. I did NOT try
anything that would have involved a system with various things missing
(like lack of VBScript), but I did play around with alternate ins
[Martin v. Löwis]
> I'd like to encourage feedback on whether the Windows installer works
> for people. It replaces the VBScript part in the MSI package with native
> code, which ought to drop the dependency on VBScript, but might
> introduce new incompatibilities.
[Tim Peters]
> Worked fine here.
[Martin v. Löwis]
>> I'd like to encourage feedback on whether the Windows
>> installer works for people. It replaces the VBScript part in the
>> MSI package with native code, which ought to drop the dependency on
>> VBScript, but might introduce new incompatibilities.
[Tim Peters]
> Worked fine
[Martin v. Löwis]
> I'd like to encourage feedback on whether the Windows installer works
> for people. It replaces the VBScript part in the MSI package with native
> code, which ought to drop the dependency on VBScript, but might
> introduce new incompatibilities.
Worked fine here. Did an all-de
Anthony Baxter wrote:
On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.1 (release candidate 1).
Python 2.4.1 is a bug-fix release. See the release notes at the website
(also available as Misc/NEWS in the source distribution) for deta
12 matches
Mail list logo
