[pypy-dev] what does the debug cycle look like?

Maciej Fijalkowski fijall at gmail.com
Tue Aug 14 10:59:43 CEST 2012

On Tue, Aug 14, 2012 at 7:11 AM, Brandon Rhodes <brandon at rhodesmill.org> wrote:
> Alex Gaynor <alex.gaynor at gmail.com> writes:
>> The trick is tests!  Tests can be run without translating (actually
>> the whole interpreter can, but we like tests :D).  Just run `pytest.py
>> pypy/module/numpypy/` and you're running the tests, they take like a
>> minute or two, which is way too long IMO, but it's totally serviceable
>> for iterative development.  The only reason we ever translate is to
>> asses the performance of something.
> Ah!  That very nearly makes sense - tell me if this is what you meant:
> the tests are not run against the translated, baked-in version of
> numpypy sitting inside my pypy interpreter and that takes hours to
> rebuild, but against the raw numpypy code - both rpython and normal
> Python - that is sitting on the disk and that I can have just edited?
> --
> Brandon Rhodes      brandon at rhodesmill.org      http://rhodesmill.org/brandon
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> http://mail.python.org/mailman/listinfo/pypy-dev


I appreciate you think we're super humans and can write code that can
only be tested in 30min (not sure why your translation take so long),
but we're not. We're very much into having a very short feedback loop.


More information about the pypy-dev mailing list