> One thing that occurs to me as I rebuild 1.6 is that it would be real nice > to be able to query the interpreter for the compilation flags at runtime so > I could be more certain I was comparing apples and apples. In my case, the > last time I built 1.6 was June 2000, so I have no idea what my compilation > flags were. I can tell by the startup message that it was compiled with gcc > 2.95.3, but not what optimization flags were used. If you did a full "make install" then and the results are still around, look in <prefix>/lib/python1.6/config/Makefile . --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