A prerelease of the Python2.0b1 Windows installer is now available via anonymous FTP, from python.beopen.com file /pub/windows/beopen-python2b1p1-20000901.exe 5,766,988 bytes Be sure to set FTP Binary mode before you get it. This is not *the* release. Indeed, the docs are still from some old pre-beta version of Python 1.6 (sorry, Fred, but I'm really sleepy!). What I'm trying to test here is the installer, and the basic integrity of the installation. A lot has changed, and we hope all for the better. Points of particular interest: + I'm running a Win98SE laptop. The install works great for me. How about NT? 2000? 95? ME? Win64 <shudder>? + For the first time ever, the Windows installer should *not* require adminstrator privileges under NT or 2000. This is untested. If you log in as an adminstrator, it should write Python's registry info under HKEY_LOCAL_MACHINE. If not an adminstrator, it should pop up an informative message and write the registry info under HKEY_CURRENT_USER instead. Does this work? This prerelease includes a patch from Mark Hammond that makes Python look in HKCU before HKLM (note that that also allows users to override the HKLM settings, if desired). + Try python lib/test/regrtest.py test_socket is expected to fail if you're not on a network, or logged into your ISP, at the time your run the test suite. Otherwise test_socket is expected to pass. All other tests are expected to pass (although, as always, a number of Unix-specific tests should get skipped). + Get into a DOS-box Python, and try import Tkinter Tkinter._test() This installation of Python should not interfere with, or be damaged by, any other installation of Tcl/Tk you happen to have lying around. This is also the first time we're using Tcl/Tk 8.3.2, and that needs wider testing too. + If the Tkinter test worked, try IDLE! Start -> Programs -> Python20 -> IDLE. + There is no time limit on this installation. But if you use it for more than 30 days, you're going to have to ask us to pay you <wink>. windows!-it's-not-just-for-breakfast-anymore-ly y'rs - tim
On Fri, Sep 01, 2000 at 07:34:46AM -0400, Tim Peters wrote:
+ I'm running a Win98SE laptop. The install works great for me. How about NT? 2000? 95? ME? Win64 <shudder>?
It runs fine under Win98 (FE) on my laptop.
+ Try python lib/test/regrtest.py
No strange failures.
Correctly uses 8.3.2, and not the 8.1 (or so) that came with Python 1.5.2
+ If the Tkinter test worked, try IDLE! Start -> Programs -> Python20 -> IDLE.
Works, too. I had a funny experience, though. I tried to quit the interpreter, which I'd started from a DOS box, using ^Z. And it didn't exit. And then I started IDLE, and IDLE started up, the menus worked, I could open a new window, but I couldn't type anything. And then I had a bluescreen. But after the reboot, everything worked fine, even doing the exact same things. Could just be windows crashing on me, it does that often enough, even on freshly installed machines. Something about bad karma or something ;)
+ There is no time limit on this installation. But if you use it for more than 30 days, you're going to have to ask us to pay you <wink>.
windows!-it's-not-just-for-breakfast-anymore-ly y'rs - tim
"Hmmm... I think I'll call you lunch." (Well, Windows may not be green, but it's definately not ripe yet! Not for me, anyway :) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
Works, too. I had a funny experience, though. I tried to quit the interpreter, which I'd started from a DOS box, using ^Z. And it didn't exit.
Really? It didn't exit? What had you done before? I do this all the time without problems.
Well, Fredrik Lundh also had some blue screens which he'd reduced to a DECREF of NULL in _tkinter. Buyt not fixed, so this may still be lurking. On the other hand your laptop might have been screwy already by that time... --Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)
On Fri, Sep 01, 2000 at 12:05:21PM -0500, Guido van Rossum wrote:
Works, too. I had a funny experience, though. I tried to quit the interpreter, which I'd started from a DOS box, using ^Z. And it didn't exit.
Really? It didn't exit? What had you done before? I do this all the time without problems.
I remember doing 'dir()' and that's it... probably hit a few cursorkeys out of habit. I was discussing something with a ^@#$*(*#%* suit (the not-very-intelligent type) and our CEO (who was very interested in the strange windows, because he thought I was doing something with ADSL :) at the same time, so I don't remember exactly what I did. I might have hit ^D before ^Z, though I do remember actively thinking 'must use ^Z' while starting python, so I don't think so. When I did roughly the same things after a reboot, all seemed fine. And yes, I did reboot after installing, before trying things the first time.
The bluescreen came after my entire explorer froze up, so I'm not sure if it has to do with python crashing. I found it particularly weird that my 'python' interpreter wouldn't exit, and the IDLE windows were working (ie, Tk working) but not accepting input -- they shouldn't interfere with each other, should they ? My laptop is reasonably stable, though somethines has some strange glitches when viewing avi/mpeg's, in particular DVD uhm, 'backups'. But I'm used to Windows crashing whenever I touch it, so all in all, I think this:
On the other hand your laptop might have been screwy already by that time...
Since all was fine after a reboot, even doing roughly the same things. I'll see if I can hit it again sometime this weekend. (A full weekend of Python and Packing ! No work ! Yes!) And I'll do my girl a favor and install PySol, so she can give it a good testing :-) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
On Fri, Sep 01, 2000 at 07:34:46AM -0400, Tim Peters wrote:
+ I'm running a Win98SE laptop. The install works great for me. How about NT? 2000? 95? ME? Win64 <shudder>?
It runs fine under Win98 (FE) on my laptop.
+ Try python lib/test/regrtest.py
No strange failures.
Correctly uses 8.3.2, and not the 8.1 (or so) that came with Python 1.5.2
+ If the Tkinter test worked, try IDLE! Start -> Programs -> Python20 -> IDLE.
Works, too. I had a funny experience, though. I tried to quit the interpreter, which I'd started from a DOS box, using ^Z. And it didn't exit. And then I started IDLE, and IDLE started up, the menus worked, I could open a new window, but I couldn't type anything. And then I had a bluescreen. But after the reboot, everything worked fine, even doing the exact same things. Could just be windows crashing on me, it does that often enough, even on freshly installed machines. Something about bad karma or something ;)
+ There is no time limit on this installation. But if you use it for more than 30 days, you're going to have to ask us to pay you <wink>.
windows!-it's-not-just-for-breakfast-anymore-ly y'rs - tim
"Hmmm... I think I'll call you lunch." (Well, Windows may not be green, but it's definately not ripe yet! Not for me, anyway :) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
Works, too. I had a funny experience, though. I tried to quit the interpreter, which I'd started from a DOS box, using ^Z. And it didn't exit.
Really? It didn't exit? What had you done before? I do this all the time without problems.
Well, Fredrik Lundh also had some blue screens which he'd reduced to a DECREF of NULL in _tkinter. Buyt not fixed, so this may still be lurking. On the other hand your laptop might have been screwy already by that time... --Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)
On Fri, Sep 01, 2000 at 12:05:21PM -0500, Guido van Rossum wrote:
Works, too. I had a funny experience, though. I tried to quit the interpreter, which I'd started from a DOS box, using ^Z. And it didn't exit.
Really? It didn't exit? What had you done before? I do this all the time without problems.
I remember doing 'dir()' and that's it... probably hit a few cursorkeys out of habit. I was discussing something with a ^@#$*(*#%* suit (the not-very-intelligent type) and our CEO (who was very interested in the strange windows, because he thought I was doing something with ADSL :) at the same time, so I don't remember exactly what I did. I might have hit ^D before ^Z, though I do remember actively thinking 'must use ^Z' while starting python, so I don't think so. When I did roughly the same things after a reboot, all seemed fine. And yes, I did reboot after installing, before trying things the first time.
The bluescreen came after my entire explorer froze up, so I'm not sure if it has to do with python crashing. I found it particularly weird that my 'python' interpreter wouldn't exit, and the IDLE windows were working (ie, Tk working) but not accepting input -- they shouldn't interfere with each other, should they ? My laptop is reasonably stable, though somethines has some strange glitches when viewing avi/mpeg's, in particular DVD uhm, 'backups'. But I'm used to Windows crashing whenever I touch it, so all in all, I think this:
On the other hand your laptop might have been screwy already by that time...
Since all was fine after a reboot, even doing roughly the same things. I'll see if I can hit it again sometime this weekend. (A full weekend of Python and Packing ! No work ! Yes!) And I'll do my girl a favor and install PySol, so she can give it a good testing :-) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
participants (3)
-
Guido van Rossum -
Thomas Wouters -
Tim Peters