I just noticed SF bug #850964, which Fred kindly fixed (back in April)... except he did it by modifying optparse.py, which is a no-no. As it says in the comment at the top: # Python developers: please do not make changes to this file, since # it is automatically generated from the Optik source code. Luckily, I've already fixed this bug in the Optik CVS, very similarly to Fred's fix. So the fact that optparse.py will be clobbered sooner or later doesn't really matter in this case. But it might have! Greg -- Greg Ward <gward at python.net> http://www.gerg.ca/ Sure, I'm paranoid... but am I paranoid ENOUGH?
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