tag:blogger.com,1999:blog-3971202189709462152.post7283625923182122073..comments2024-03-11T12:50:02.036+01:00Comments on PyPy Status Blog: PyPy 1.4.1Carl Friedrich Bolz-Tereickhttp://www.blogger.com/profile/00518922641059511014noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-3971202189709462152.post-4634784293968792922011-01-29T11:23:45.490+01:002011-01-29T11:23:45.490+01:00Andrei: not directly. We played at some point wit...Andrei: not directly. We played at some point with translating RPython code to Javascript, but it didn't give enough benefits (because it's not full Python that we can translate, just "RPython"). The alternative would be to translate the whole PyPy interpreter to Javascript, but that would give a result that is both huge (in term of download size) and horribly slow (100x slower than Javascript maybe).Armin Rigohttps://www.blogger.com/profile/06300515270104686574noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-16427929270458002572011-01-28T21:08:55.614+01:002011-01-28T21:08:55.614+01:00Hello,
sorry, I'm a bit new here - is it poss...Hello,<br /><br />sorry, I'm a bit new here - is it possible that PyPy makes Python run in a browser? Somehow "translating" all the Python into Javascript?<br /><br />I'm wondering because I saw you run, for example, CLI, so perhaps PyPy may somehow enable Python in a browser?Andreinoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-40830352855223302802010-12-28T17:00:40.260+01:002010-12-28T17:00:40.260+01:00I compiled 1.4.1 on Win32 using Visual C++ 2010.
...I compiled 1.4.1 on Win32 using Visual C++ 2010.<br /><br />Do you want to add it to the download page?<br /><br />To whom shall I send it?<br /><br />Happy new year.shadingerhttps://www.blogger.com/profile/14292732619477654911noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-54750203520540442452010-12-22T15:14:26.158+01:002010-12-22T15:14:26.158+01:00Thanks for PyPy 1.4.1. I reported two issues conce...Thanks for PyPy 1.4.1. I reported two issues concerning buildout with PyPy 1.4, and they all got fixed! <br /><br />So PyPy 1.4.1 is now compatible with buildout, which is really convenient as it makes it easy for me to test other projects.Martijn Faassennoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-47973663533831774132010-12-22T14:59:25.899+01:002010-12-22T14:59:25.899+01:00Actually, hashlib.sha was not the same as sha.sha:...Actually, hashlib.sha was not the same as sha.sha: the former used to be a ctypes call to the OpenSSL lib, whereas the latter uses our built-in sha implementation. So hashlib.sha was faster in theory, but killed by the overhead of using ctypes. Now, at least in a default version of pypy, the hashlib.md5 and .sha are redirected to the built-in md5.md5 and sha.sha.<br /><br />Another issue was that with the built-in md5.md5 and sha.sha, on 64-bit, there was a 1.5x speed impact due to the C compiler not recognizing an expression that was meant to be a 32-bit integer rotation.<br /><br />I guess that http://speed.pypy.org don't show this because they use directly md5.md5 or sha.sha, and are on 32-bit.Armin Rigohttps://www.blogger.com/profile/06300515270104686574noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-36104269264039763772010-12-22T14:10:01.007+01:002010-12-22T14:10:01.007+01:00I'm interested in the performance improvement ...I'm interested in the performance improvement in hashlib.sha. I haven't seen that one before on http://speed.pypy.org . Could you give me more details?<br /><br />Regards,<br /><br />ZookoAnonymoushttps://www.blogger.com/profile/17046522562803939443noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-58830987601749288112010-12-22T13:09:59.341+01:002010-12-22T13:09:59.341+01:00There are still a number of branches that have not...There are still a number of branches that have not been merged into trunk yet: at least fast-forward (Python 2.7), jit-unroll-loops (better JITting of arithmetic and short loops), arm-backend (JIT support on ARM) and jitypes2 (turn ctypes calls into real assembler-level calls with the JIT). There is also the stackless+JIT integration pending. Finally the sprint will also be a place to try out and run some applications. So it's not like we are out of work :-)Armin Rigohttps://www.blogger.com/profile/06300515270104686574noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-28808521560555584282010-12-22T13:00:47.273+01:002010-12-22T13:00:47.273+01:00Wow, and I thought 1.4.1 would come out after the ...Wow, and I thought 1.4.1 would come out after the january sprint!<br /><br />A christmas present :-><br /><br />What would be the focus of the january sprint then?Symbolhttps://www.blogger.com/profile/10991731639856711923noreply@blogger.com