or you might be happy with
your algo being 4x faster while being quite easy to develop (not
needing to use c).
I personally think this will be too much work on
--
Leonardo Santagada
santagada at gmail.com
___
Python-Dev mailing list
Python-Dev@
sides that, it is always very cool to see another vm project
starting,
Good Luck
--
Leonardo Santagada
santagada at gmail.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscr
k using ld preload to use
another memory manager that respond the way needed... at least that
was what I was told today at lunch. (if ulimit is not enough for any
reason).
--
Leonardo Santagada
santagada at gmail.com
___
Python-Dev mailing l
r amount of variables to any comparison.
I would sugest compiling 2.5 and 2.6 from source, run the benchmark x
times and take the smallest time of each test (so os and cpu scalling
don't influence so much the benchmark) and then comparing the results.
--
Leonardo
ve to compile PyObjC from source, but this can be easily fixed.
Talking about this, why not just point pythonmac.org to python.org
python version and release the packages as eggs on cheeseshop?
(specially py2exe and pyobjc as those are usually heavily needed on
macs).
--
Leonardo Sant
variables at the time of failure.
Maybe move the "test_*.py" search into the unittest module.
Those ideas are cool too.
all those features are already implemented in py.test and most
probably also on nose. Why not just port those to unittest? is this
even being considered?
--
Leonardo