> For anything that takes more than half a second or so, it's usually a big win and can turn minutes into seconds.
As a counter to this, I purposefully try to use CPython in order to force me to find algorithmically optimal solutions. It's a useful way to learn.
Re:Improving SyntaxError in PyPy
by daveFNbuck on Thursday April 12, 2018 @01:54AM
(#16818369)
Having a faster interpreter also allows me to play with the numbers more to get a better feel and understanding for the problem. I think that's the point of Project Euler, but I understand your point of view.
Do any of the Project Euler questions actually require lengthy computation, or is that more a sign that one should be looking for some mathematical insight that leads to a more efficient computation?
Re:Improving SyntaxError in PyPy
by daveFNbuck on Thursday April 12, 2018 @12:40AM
(#16818035)
Most of them don't require lengthy computation, but some of them did for me. I know at least some of the time that's because I didn't know enough math, but sometimes I had the same algorithm as the other people in the solution thread but with much slower runtimes. I think numpy gives a bigger speedup than PyPy for a lot of the problems.
PyPy won't change your data structures and algorithms, so it's not finding mathematical insight.
Yes that’s the point I was making. Maybe you intended your comment to be a sibling to mine.
Re:Improving SyntaxError in PyPy
by daveFNbuck on Thursday April 12, 2018 @01:47AM
(#16818338)
It seems that you're saying that I should be finding mathematical insight instead of using PyPy, while xapata is saying that if my code runs fast in PyPy then I've already found enough mathematical insight.
I also use it at home to solve Project Euler problems. For anything that takes more than half a second or so, it's usually a big win and can turn minutes into seconds.