tag:blogger.com,1999:blog-3971202189709462152.post2083371215707583264..comments2024-03-11T12:50:02.036+01:00Comments on PyPy Status Blog: Report back from our surveyCarl Friedrich Bolz-Tereickhttp://www.blogger.com/profile/00518922641059511014noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-3971202189709462152.post-12448179779897141882011-06-15T11:10:31.482+02:002011-06-15T11:10:31.482+02:00Lack of support for numpy and scipy are what keep ...Lack of support for numpy and scipy are what keep me from using pypy. Am using python for analysis of ultra high throughput DNA sequencing data.<br /><br />Would be very curious to see how much performance I could gain by using pypy.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-14728148534066474742011-06-11T02:06:22.982+02:002011-06-11T02:06:22.982+02:00What about a FFI to C or C++? Something like LuaJi...What about a FFI to C or C++? Something like LuaJit's FFI, which is really good.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-16146732568655534782011-06-09T10:41:33.173+02:002011-06-09T10:41:33.173+02:00@⚛ The line might be blurry, but "I'm usi...@⚛ The line might be blurry, but "I'm using PyPy for X" or "I'm not using PyPy for X, because ..." is on topic. While "Python can be used for X" or "Python can't be used for X, because ..." is not on topic. This is a fine line between language implementation (which is PyPy about) and language design (which PyPy is not about, python-dev/python-list/python-ideas mailing lists are about that).<br /><br />Cheers,<br />fijalMaciej Fijalkowskihttps://www.blogger.com/profile/11410841070239382771noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-30718468273535613362011-06-09T10:38:38.012+02:002011-06-09T10:38:38.012+02:00@Maciej Fijalkowski: I will of course do what you ...@Maciej Fijalkowski: I will of course do what you ask, but I would like you to point me to at least one blog comment that: (1) Is initially saying that Python/PyPy is *good* for task X, and (2) You or somebody else from the PyPy team wrote "Please take the discussion about X somewhere else".<br /><br />Thanks<br />⚛Jan Ziak (atomsymbol)https://www.blogger.com/profile/00398184141815003668noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-18338199308780439992011-06-09T08:58:48.676+02:002011-06-09T08:58:48.676+02:00@⚛ Not even trying to argue with you, comments on ...@⚛ Not even trying to argue with you, comments on this blog is not a proper place to discuss whether Python is good for high-reliability systems. Please take the discussion somewhere else<br /><br />Thanks,<br />fijalMaciej Fijalkowskihttps://www.blogger.com/profile/11410841070239382771noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-1565223452424158732011-06-09T08:22:26.490+02:002011-06-09T08:22:26.490+02:00@Marko Tasic: If I may ask a question. You wrote t...@Marko Tasic: If I may ask a question. You wrote that you are using PyPy for highly reliable systems. I know what you mean, but it seems to me that certain features of Python are in contradiction with high reliability. For example, it is in practice impossible to know at compile-time whether you misspelled a variable or parameter in Python source code. My question would be: why are you using a language which has only rudimentary compile-time error detection to implement a high reliability system?Jan Ziak (atomsymbol)https://www.blogger.com/profile/00398184141815003668noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-51164076734390851442011-06-08T21:42:40.485+02:002011-06-08T21:42:40.485+02:00I'm using pypy 1.5 with jit in production for ...I'm using pypy 1.5 with jit in production for highly reliable and responsive distributed and decentralized systems, and I'm happy with it.Marko Tasichttps://www.blogger.com/profile/11624217750420896579noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-32690445198272975732011-06-08T21:40:11.512+02:002011-06-08T21:40:11.512+02:00This comment has been removed by the author.Marko Tasichttps://www.blogger.com/profile/11624217750420896579noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-91964061793317617922011-06-08T19:05:10.228+02:002011-06-08T19:05:10.228+02:00@Maciej Fijalkowski: Ok, thanks for the clarificat...@Maciej Fijalkowski: Ok, thanks for the clarification.Jan Ziak (atomsymbol)https://www.blogger.com/profile/00398184141815003668noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-12164681381007498642011-06-08T15:20:44.348+02:002011-06-08T15:20:44.348+02:00@⚛ I think Alex was simply too lazy to count :-) A...@⚛ I think Alex was simply too lazy to count :-) At some point there were 600 respondents and roughly 10% of them used pypy in production, which is pretty good IMO.Maciej Fijalkowskihttps://www.blogger.com/profile/11410841070239382771noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-7514196597938704652011-06-08T15:16:03.272+02:002011-06-08T15:16:03.272+02:00"... we're very pleased to report that a ..."... we're very pleased to report that a number of you guys are happilly running PyPy in production"<br /><br />You decided to keep the actual number of users a secret? Why?Jan Ziak (atomsymbol)https://www.blogger.com/profile/00398184141815003668noreply@blogger.comtag:blogger.com,1999:blog-3971202189709462152.post-76823994298187105632011-06-08T11:18:53.143+02:002011-06-08T11:18:53.143+02:00I'm surprised more people didn't mention P...I'm surprised more people didn't mention Python 3 support as a big breaker. I certainly did.Paulhttps://www.blogger.com/profile/17889592791004041104noreply@blogger.com