Re: [Python-Dev] Pie-thon benchmark code ready
At 16:50 31.12.2003 -0800, Guido van Rossum wrote:
(There's also an issue with the distinction between repr() of int and long, which will disappear in Python 3.0, and repr() of str vs. unicode, which already doesn't exist in Jython. So I predict that the benchmark currently doesn't have a chance of passing on Jython. (But it would be interesting to time it anyway -- simply disable the raises in b0.check() and in b5.check().)
Jython is still not up to run it. But yes it would be an interesting thing. Indeed in any case some other things wrt representation would be a problem still: Jython 2.2a0 on java1.4.0_02 (JIT: null) Type "copyright", "credits" or "license" for more information.
u'a' 'a' def f(): pass ... f <function f 1> class X: ... pass ... X <class __main__.X 2>
...
In general <...> reprs vary.
Jython is still not up to run it. But yes it would be an interesting thing.
Maybe you could find a sponsor for Jython development...?
Indeed in any case some other things wrt representation would be a problem still:
Jython 2.2a0 on java1.4.0_02 (JIT: null) Type "copyright", "credits" or "license" for more information.
u'a' 'a' def f(): pass ... f <function f 1> class X: ... pass ... X <class __main__.X 2>
...
In general <...> reprs vary.
But I've seen enough people write code that parses <...> reprs in some way to make me think that maybe they should be standardized somewhat, at least to the point where different Python implementations should not differ gratuitously. E.g. Jython could be much closer to CPython by inserting 'at 0x'. It's not like standardizing this would close off an important implementation freedom for other Python implementation. (I won't go as far as requiring that the number should be the same as hex(id(x)). :-) --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (2)
-
Guido van Rossum -
Samuele Pedroni