Greg, Windows users, etc.: I just checked in the changes for winreg so that an object-oriented interface is presented to the user. This affects the distutils on Windows; if someone who knows about this stuff can update the winreg use, it would be really good to get that in tonight or first thing tomorrow morning!
-Fred
On 29 June 2000, Fred L. Drake, Jr. said:
I just checked in the changes for winreg so that an object-oriented interface is presented to the user. This affects the distutils on Windows; if someone who knows about this stuff can update the winreg use, it would be really good to get that in tonight or first thing tomorrow morning!
Yipes! Is it enough to "import _winreg" instead of "winreg" and continue to use the low-level interface? Or was it not implemented like that in the end?
Greg
Greg Ward writes:
Yipes! Is it enough to "import _winreg" instead of "winreg" and continue to use the low-level interface? Or was it not implemented like that in the end?
_winreg is exactly yesterday's (even this morning's) winreg, aside from the name. It passes the old regression test, so it should work fine for distutils. Is there a reason not to switch to the new winreg, or is just a matter of time availability?
-Fred
On 29 June 2000, Fred L. Drake, Jr. said:
_winreg is exactly yesterday's (even this morning's) winreg, aside from the name. It passes the old regression test, so it should work fine for distutils.
Good.
Is there a reason not to switch to the new winreg, or is just a matter of time availability?
Two reasons: 1) time availability, 2) I don't know the new API and can't test it in any case, and 3) -- no, THREE reasons! -- msvccompiler.py can either use the API provided by win32api and win32con or that provided by the-module-formerly-known-as-winreg, because they are quite similar interfaces. If we switch to the (presumably nice and OO) interface provided by winreg (not _winreg!), then compatibility with win32api/win32con for Python 1.5.2 would go away.
No wait, FOUR reasons: it ain't broken.
Greg
Greg Ward writes:
Two reasons: 1) time availability, 2) I don't know the new API and can't test it in any case, and 3) -- no, THREE reasons! -- msvccompiler.py can
I sent the note to the list so that people who can would be aware of it and could make the changes -- I really didn't expect you to make the changes. ;)
either use the API provided by win32api and win32con or that provided by the-module-formerly-known-as-winreg, because they are quite similar interfaces. If we switch to the (presumably nice and OO) interface provided by winreg (not _winreg!), then compatibility with win32api/win32con for Python 1.5.2 would go away.
This is a more substantial reason.
No wait, FOUR reasons: it ain't broken.
Counter: The old winreg has never been part of a stable release.
-Fred
On 29 June 2000, Fred L. Drake, Jr. said:
No wait, FOUR reasons: it ain't broken.
Counter: The old winreg has never been part of a stable release.
Then I will remove support for it *after* the next Python release, with winreg and _winreg.
Greg
participants (2)
-
Fred L. Drake, Jr. -
Greg Ward