fijall
Re:PyPy support for Python 3 (pypy-dev)
on Tuesday September 13, 2011 @03:02AM (#2990306)
PyPy doesn't have a specialized list for small strings. It might land one in the near future, your findings are a bit weird, but objects might be smaller because of smaller GC headers.
Cheers, fijal
Re:Global Interpreter Lock, or how to kill it
on Wednesday June 29, 2011 @04:19PM (#2711082)
This doesn't quite apply to PyPy (which doesn't have refcounting), but the point stands. In case of PyPy this is GC flags and moving GC.
Re:Global Interpreter Lock, or how to kill it
on Wednesday June 29, 2011 @04:17PM (#2711073)
"If you've got the control necessary to automatically STM things, you might as well just equally-automatically copy the Jython-style locking."
So far thinking about how to really do that automatically failed. Do you feel like providing an idea?
Re:Satellite Images of North Korea Prison Camps Find 200,000 Living as...
on Thursday May 12, 2011 @01:07PM (#2541340)
2,292,133 were in prisons in the United States in 2009 [from wikipedia]. Even though I guess conditions are better, 200 000 doesn't sound like that many after all.
Re:A brief experiment with PyPy
on Thursday May 12, 2011 @12:07PM (#2541051)
The main reason why more people are not working on this is that:
* volunteers are interested somewhere else
* nobody is willing to put money into numpy on pypy happening
Re:PyPy 1.5 Released: Catching Up
on Monday May 02, 2011 @12:26PM (#2506790)
you should have a look at scheme interpreter that was written already maybe: https://bitbucket.org/pypy/lang-scheme/overview
Re:Google Leads List of Desired Employers
on Monday March 21, 2011 @03:25PM (#2351166)
It's incredible that L'Oréal placed 40. I wouldn't want to work for a company that has non-printable name apparently.
Re:Money Won’t Buy You Health Insurance
on Monday February 21, 2011 @07:47PM (#2248066)
Importing people from anywhere else is on it's way out in the US as well. (even willingly)
Re:"Blackhole" interpreter in PyPy: new optimization in PyPy 1.3
on Monday June 28, 2010 @02:00AM (#1467215)
The thing is in case of tracing you don't record all paths taken, just the one at the hot point. So say you have if that takes every path every second go, the JIT will compile just one path at first. Then the guard will fail every second iteration, hence the blackhole. Of course at some point JIT will realize guard fails often enough and will compile another path, so you'll get a tree. And so on...