[Python-Dev] Even more prerelease Python fun on Windows!

[Tim Peters]

As below, except the new file is

    /pub/windows/beopen-python2b1p2-20000901.exe
    5,783,115 bytes

still from anonymous FTP at python.beopen.com.  The p1 version has been
removed.

+ test_popen2 should work on Windows 2000 now (turned out that,
  as feared, MS "more" doesn't work the same way across Windows
  flavors).

+ Minor changes to the installer.

+ New LICENSE.txt and README.txt in the root of your Python
  installation.

+ Whatever other bugfixes people committed in the 8 hours since
  2b1p1 was built.

Thanks for the help so far!  We've learned that things are generally working
well, on Windows 2000 the correct one of "admin" or "non-admin" install
works & is correctly triggered by whether the user has admin privileges, and
that Thomas's Win98FE suffers infinitely more blue-screen deaths than Tim's
Win98SE ever did <wink>.

Haven't heard from anyone on Win95, Windows Me, or Windows NT yet.  And I'm
downright eager to ignore Win64 for now.

-----Original Message-----
Sent: Friday, September 01, 2000 7:35 AM
To: PythonDev; Audun.Runde@sas.com
Cc: audun@mindspring.com
Subject: [Python-Dev] Prerelease Python fun on Windows!


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



_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://www.python.org/mailman/listinfo/python-dev