Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
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 question "Are you sure you want to cancel the Python 2.4.1c1 installation". This crashed msiexec.exe. I was able to reproduce this on Windows XP Professional, Service Pack 2. I could reproduce it, but I doubt I can do anything about it. When it asked whether I want to report this to MS, I did - recently, I learned what the magic procedure behind this analysis is, and that there is a good chance that this report really ends up at the developer of installer responsible for the code that crashed. I'm pretty certain it is none of my code which causes the crash (the same rule applies as with Python: it may raise an exception, bring up an error message, and so on - but it should never crash). Regards, Martin ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
"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 ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
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 the Indexing Service sometimes prevents files from being opened. Quadruple-click could also cause the problem, if you try to start multiple installers. If I wait for the download to complete and the virus check to finish, then it's AOK. That's why the third time was the charm. Ok, so it's likely incomplete download. Regards, Martin ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
"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 clicked on the 2.4.1b2 installer and that started ok. Cancelled it. > > This must have been 2.4b2, right? However, didn't you have 2.4 installed > already? Right, 2.4b2. I never updated to 2.4 on that box. OK, the problem was: I rushed the install. The package had not finished downloading, but the icon appears on the desktop as soon as the download starts. (With Opera you have to pay attention to the download status, it's rather subtle.) If I wait for the download to complete and the virus check to finish, then it's AOK. That's why the third time was the charm. -- KBK ___ 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
RE: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
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, clicked the "Cancel" button, and clicked "Yes" to the question "Are you sure you want to cancel the Python 2.4.1c1 installation". This crashed msiexec.exe. I was able to reproduce this on Windows XP Professional, Service Pack 2. Regards, -- Vincent Wehren ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
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 ok. Cancelled it. This must have been 2.4b2, right? However, didn't you have 2.4 installed already? For ducks I installed Python at D:\"Python 2.4". It installed in the correct location, also found C:\Python24 and uninstalled that. That is supposed to happen; I never tested it, though. Python and IDLE appear to run ok. Shortcuts on Run work, and file association was updated, so right clicking a .py used IDLE from Python 2.4.1c1, in no-subprocess mode. Good! Martin ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
"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 had some strange experiences. Windows2000: I downloaded the 2.4.1c1 installer to the desktop and clicked on it. It complained that it couldn't access the installer. I then clicked on the 2.4.1b2 installer and that started ok. Cancelled it. Repeated this sequence a second time. Same. The third time I clicked on 2.4.1c1 it started up and installed Python ok. For ducks I installed Python at D:\"Python 2.4". It installed in the correct location, also found C:\Python24 and uninstalled that. Python and IDLE appear to run ok. Shortcuts on Run work, and file association was updated, so right clicking a .py used IDLE from Python 2.4.1c1, in no-subprocess mode. -- KBK ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
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 install locations, repairs, uninstalls, single-user and all-user installs, and I found no problems anywhere. Nice work! Thanks! Somebody reported that it failed to update python24.dll in an update installation; not sure why this would be. Regards, Martin ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
[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. Did an all-default "all users" install, WinXP Pro > SP2, from local disk, and under an account with Admin rights. I > uninstalled 2.4 first. I suppose that's the least stressful set of > choices I could possibly have made, but at least it confirms a happy > baseline. 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 install locations, repairs, uninstalls, single-user and all-user installs, and I found no problems anywhere. Nice work! -- Michael Chermside ___ 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
RE: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
[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. Did an all-default "all users" install, > WinXP Pro SP2, from local disk, and under an account with > Admin rights. I uninstalled 2.4 first. I suppose that's the > least stressful set of choices I could possibly have made, > but at least it confirms a happy baseline. Also works fine for me with: * WinXP Pro SP2, from local disk, with admin rights, all defaults, over the top of 2.4.0 * Win2k SP4, from network disk, without admin rights, all defaults, with no previous 2.4 * Win2k SP4 (different machine), from local disk, with admin rights, defaults apart from skipped test suite, over the top of 2.4.0 =Tony.Meyer ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
[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-default "all users" install, WinXP Pro SP2, from local disk, and under an account with Admin rights. I uninstalled 2.4 first. I suppose that's the least stressful set of choices I could possibly have made, but at least it confirms a happy baseline. ___ 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
Re: [Python-Dev] RELEASED Python 2.4.1, release candidate 1
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 details of the bugs squished in this release. 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. Regards, Martin ___ 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
