Vincent Delecroix wrote: > Then I guess the reason of the slowdown comes from the change in > the integer types in Python 3 and the way we handle the conversion > from Python integers to Sage integers
This may be part of it, but I don't think it explains everything: sage: a = 1 sage: %timeit a+a The slowest run took 103.92 times longer than the fastest. This could mean that an intermediate result is being cached. 10000000 loops, best of 3: 57.4 ns per loop vs sage: %timeit a+a The slowest run took 93.42 times longer than the fastest. This could mean that an intermediate result is being cached. 10000000 loops, best of 5: 65.1 ns per loop -- Marc -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/qrdbq5%24383n%241%40blaine.gmane.org.