On Sun, Sep 30, 2012 at 8:28 PM, Antoine Pitrou email@example.com wrote:
On Sun, 30 Sep 2012 19:12:47 -0400 Brett Cannon firstname.lastname@example.org wrote:
### mako_v2 ### Min: 0.137584 -> 0.287701: 2.09x slower Avg: 0.140620 -> 0.293204: 2.09x slower Significant (t=-296.14) Stddev: 0.00243 -> 0.00272: 1.1195x larger
Note that Mako can use the Markupsafe library for faster operation. This will skew the result if one of your Pythons has Markupsafe installed and the other does not.
Should probably have the benchmark print out a warning when markupsafe is used. Turns out I have it installed in my user directory for Python 2.7 so that probably came into play.
Perhaps the benchmark runner should launch its subtests in a controlled environment to avoid such issues?
If we had venv in Python 2.7 that might be easy to do, but otherwise is there an easy way without having to try to pull in virtualenv or something crazy like a chroot or something?
(shipping a copy of Markupsafe would not be very practical, because it
has a C extension)
-- Software development and contracting: http://pro.pitrou.net
Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org