Re: [Python-Dev] peps: PEP 432 updates in response to initial comments
On Fri, 28 Dec 2012 14:54:55 -0500
Terry Reedy
4. Running ./python_d from within a PCBuild/python_d interactive window and on a regular disk averages .10 seconds. The slowdown is probably a mixture of disk access and extra debug code, but is not bad. There is no flashing (probably because there already is a window, whereas on Windows IDLE runs code within a windowless pythonw process) and ^C works. This is definitely a better environment for this type of test ;-).
You'd get more meaningful numbers by using a non-debug build (PCBuild/python.exe, I guess). Our debugging additions + the lack of compiler optimizations butcher performance. It would be extra nice if you had numbers comparing 3.3, 3.2 and 2.7 (under Windows, that is). Regards Antoine.
participants (1)
-
Antoine Pitrou