> I have a different suggestion: screw it. getopt keeps creating problems on > GNUish systems too, because without the POSIXLY_CORRECT envar set, the GNU > getopt shuffles all the "option strings" to the front, making a mess of, > e.g., > > python myprog.py -v > > The Python source tree already has its own getopt implementation > (Python/getopt.c) -- let's rename its contained function to PyOS_Getopt, get > rid of the irritating __BEOS__ #ifdef'ery therein, prototype it the way we > like, and have Python use that instead on all systems. Every second we've > spent tracking down problems with platform-supplied getopts has been a waste > of time. Excellent. After 2.0. --Guido van Rossum (home page: http://www.python.org/~guido/)
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