Your message dated Tue, 24 Apr 2007 11:58:13 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#256781: Your bugreport on ipython
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ipython
Version: 0.6.0-1
Severity: normal
[I manually changed the input prompts to >>> and removed the
output labels.]
On a 2.0GHz P4 laptop (speedstep disabled) running mostly testing:
Python 2.3.4 (#2, May 29 2004, 03:31:27)
Type "copyright", "credits" or "license" for more information.
IPython 0.6.0 -- An enhanced Interactive Python.
>>> from timeit import *
>>> from time import *
>>> t=Timer("pass","pass",timer=time)
>>> t.timeit(1000000)
0.15831089019775391
>>> t.repeat(1,1000000)
[0.079621076583862305]
Note the factor of two difference! It's consistent:
>>> t.timeit(1000000)
0.14923691749572754
>>> t.repeat(1,1000000)
[0.080674886703491211]
>>> for i in range(3):
... t.timeit(1000000)
0.15053701400756836
0.15190696716308594
0.15034103393554688
>>> t.repeat(3,1000000)
[0.080902099609375,
0.081040859222412109,
0.080629110336303711]
And it happens with timer=clock too:
>>> t2=Timer("pass","pass",timer=clock)
>>> t2.timeit(1000000)
0.11000000000000032
>>> t2.repeat(3,1000000)
[0.079999999999999627, 0.080000000000000071, 0.090000000000000302]
It also happens with statements other than "pass". The ratio is
different then, and sometimes the repeat version takes longer
(in one case, consistently 20% longer).
This doesn't happen when the above is run in plain python.
And it doesn't happen using ipython on a dual Xeon machine I have
access to, which also runs Debian testing.
Any ideas what's up? I've looked at timeit.py and can't see how this
is possible... Let me know if I can help debug it.
Dan
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=C, LC_CTYPE=C
Versions of packages ipython depends on:
ii python 2.3.4-1 An interactive high-level object-o
-- no debconf information
--- End Message ---
--- Begin Message ---
Heya,
>> long time ago you've reported a "funny" behavior in ipython as a bug[1].
>> I was not able to reproduce this bug in ipython 0.8.0-1, so I think
>> it was fixed silently. Therefore I'll close the bugs within the next
>> days. If you think that the bug still exists, please let us know.
>>
>
> I think it's fine to close it. I still see a small bias, but it isn't
> worth worrying about.
>
Thanks for your reply. The bug will be closed with this mail, please
reopen it if the problem arises again.
Best regards,
Bernd Zeimetz
--
Bernd Zeimetz
<[EMAIL PROTECTED]> <http://bzed.de/>
--- End Message ---
