On 29 June 2000, Fred L. Drake, Jr. said:
>
> Greg Ward wrote in a checkin message:
> > On second thought, first try for _winreg, and then winreg. Only if both
> > fail do we try for win32api/win32con. If *those* both fail, then we don't
> > have registry access. Phew!
>
> Guido van Rossum writes on python-dev:
> > Is this smart? Doesn't the new winreg have a very different I/F than
> > the old one?
>
> No, this is bad. It *will* break with winreg; if _winreg isn't
> available, it should use the win32api/win32con/whatever stuff; it's a
> Python 1.5.2 interpreter at that point.
What if it's a 1.6a1 or 1.6a2 interpreter? Presumably people will try
Distutils 0.9 with them. Should I remove that feature now that 0.9 is
out, but before Python 2.0b1?
Greg
--
Greg Ward - software developer gward@mems-exchange.org
MEMS Exchange / CNRI voice: +1-703-262-5376
Reston, Virginia, USA fax: +1-703-262-5367
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4