perf.py - I'll look into this. At this point we'll need to refactor them any ways as there are a few dependencies on internal Microsoft stuff the IronPython Team didn't create. Thanks, Dave -----Original Message----- From: Maciej Fijalkowski [mailto:fijall at gmail.com] Sent: Wednesday, February 24, 2010 10:51 AM To: Dave Fugate Cc: python-dev at python.org Subject: Re: [Python-Dev] Mercurial repository for Python benchmarks On Wed, Feb 24, 2010 at 12:12 PM, Dave Fugate <dfugate at microsoft.com> wrote: > Would there be any interest in accepting IronPython's in-house benchmarks into this repository as well? Internally we run the usual suspects (PyStone, PyBench, etc), but we also have a plethora of custom benchmarks we've written that also happen to run under CPython. > > My best, > > Dave > From my perspective the more we have there the better. We might not run all of them on nightly run for example (we as in PyPy). Are you up to adhering to perf.py expectation scheme? (The benchmark being runnable by perf.py) Cheers, fijal
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