[Aahz] > A> Hrm. Based on previous comments, particularly from the Timbot, > A> I'm wondering whether the linkage between !debugging and > A> optimizing is too tight in Python, and whether constructs like > A> this should be deprecated. Seems to me that there will > A> definitely be times you want debugging output when you're running > A> -O. [Jeremy] > There definitely are times when we want debugging outputs when running > with -O, but we live with restarting the server in those cases. There > is such a big performance benefit to not even compiling the code when > -O is enabled. +1 on making debugging and optimization should be separately selectable options. -1 in going about it in a hurry. This should be fixed the next time we're doing major surgery on the compiler. --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