> You may be right. Still, this patch solves the immediate problem in a > reasonably clean way, and I urge that it should go in. We can do a > more complete reorganization of the build process later. (I'll help with > that; I'm pretty expert with autoconf and friends.) I expect Andrew's code to go in before 2.1 is released. So I don't see a reason why we should hurry and check in a stop-gap measure. --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