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. -Fred -- Fred L. Drake, Jr. <fdrake at beopen.com> BeOpen PythonLabs Team Member
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