Re: [pypy-dev] SSL in the stdlib

On Thu, Jan 9, 2014 at 8:20 AM, Alex Gaynor wrote: > Hey all, > > There are a number of serious security improvements that have gone into the > stdlib SSL module in Python 3. For reasons that defy understanding, the > CPython maintainers have decided not to backport them to Python 2. > > I'd like

[pypy-dev] ctypes create_string_buffer

import ctypes as C s1= "0"* 1024* 1024* 10 # mem engross add 10M bytes b1= C.create_string_buffer(s1 ) # CPU 1 core 100% and mem engross add 300M bytes ? I don't know! please talk me, thanks very match I'm chinese, english is not good, sorry! ___ py

[pypy-dev] Boost.Python and PyPy -- status?

Hi there, I have written a (C)Python extension using Boost::Python, and would like to get it working on PyPy. I came across [1], but that's probably a bit out of date, and the link given there discussing the status then[2] doesn't work any more. Is there an up-to-date status page? Or, does anyone

Re: [pypy-dev] Boost.Python and PyPy -- status?

On Thu, 2014-01-09 at 16:59 +, Toby St Clere Smithe wrote: > > I have written a (C)Python extension using Boost::Python, and would > like to get it working on PyPy. I came across [1], but that's probably > a bit out of date, and the link given there discussing the status > then[2] doesn't work

Re: [pypy-dev] Boost.Python and PyPy -- status?

Hi Yury, "Yury V. Zaytsev" writes: > Did you actually try it? Hah, no! I wasn't that optimistic! > I have found that cpyext has seen huge improvements in the last years. > This summer, I've managed to compile some rather complex > Cython-generated code with minor manual changes... This certain

[pypy-dev] cppyy and callbacks

Hi all, So I've been working on trying to develop PyPy bindings for the Bullet physics library (http://bulletphysics.org/) using cppyy. So far, after a bit of an initial learning curve, I was able to put together a configuration that maps almost all of the standard Bullet classes and functions, a

Re: [pypy-dev] Boost.Python and PyPy -- status?

On Thu, Jan 9, 2014 at 8:05 PM, Toby St Clere Smithe wrote: > Hi Yury, > > "Yury V. Zaytsev" writes: >> Did you actually try it? > > Hah, no! I wasn't that optimistic! > >> I have found that cpyext has seen huge improvements in the last years. >> This summer, I've managed to compile some rather c

Re: [pypy-dev] Boost.Python and PyPy -- status?

Every tried Shiboken? My guess is that it'd work better with cpyext thatn Boost::Python, since there's less black magic in the background. On Thu, Jan 9, 2014 at 10:59 AM, Toby St Clere Smithe wrote: > Hi there, > > I have written a (C)Python extension using Boost::Python, and would like > to ge

Re: [pypy-dev] Boost.Python and PyPy -- status?

Hi fijal, Maciej Fijalkowski writes: > I'm less optimistic. Boost::Python uses tons of internal stuff as far > as I know. We really discourage people from using it, because it's a) > slow b) prone to not behave exactly like CPython and c) be incomplete. That's a shame, not least because boost::p

Re: [pypy-dev] Boost.Python and PyPy -- status?

Ryan Gonzalez writes: > Every tried Shiboken? My guess is that it'd work better with cpyext thatn > Boost::Python, since there's less black magic in the background. No, I'd not heard of Shiboken, but it does look like an interesting project. As I wrote in my reply to fijal, I quite like boost::py

Re: [pypy-dev] Boost.Python and PyPy -- status?

Shiboken was written for the official Python Qt bindings(PySide). They actually were originally using Boost::Python, but they switched to Shiboken because the binaries were a lot smaller. Unfortunately, there isn't too much documentation. Here are some links: http://seanfisk.com/pyside-docs/shibok

Re: [pypy-dev] Boost.Python and PyPy -- status?

Hi Ryan, Ryan Gonzalez writes: > Shiboken was written for the official Python Qt bindings(PySide). They > actually were originally using Boost::Python, but they switched to Shiboken > because the binaries were a lot smaller. Unfortunately, there isn't too > much documentation. Here are some links

Re: [pypy-dev] cppyy and callbacks

What about the CINT backend? https://bitbucket.org/pypy/pypy/src/52bbec630c1faec5ea0c1772872411de541d507f/pypy/module/cppyy/test/test_cint.py On Thu, Jan 9, 2014 at 12:14 P

Re: [pypy-dev] Boost.Python and PyPy -- status?

2014/1/9 Toby St Clere Smithe > Hi there, > > I have written a (C)Python extension using Boost::Python, and would like > to get it working on PyPy. I came across [1], but that's probably a bit > out of date, and the link given there discussing the status then[2] > doesn't work any more. Is there

Re: [pypy-dev] cppyy and callbacks

Hi Alex, I have to say, I'm pretty impressed with how smoothly it all works! good to hear. The one main issue I'm left with at this point, however, is that for any sort of real application, Bullet makes substantial use of callbacks (both in the form of some global C++ function pointers as we

Re: [pypy-dev] cppyy and callbacks

Hi Ryan, What about the CINT backend? the way we "jit" code with CINT, is by generating a temporary file, then running the dictionary generator over it, and pulling everything through the C++ compiler. Works, but ... Also, the CINT backend carries more dependencies than strictly necessary, fo

Re: [pypy-dev] cppyy and callbacks

I'd looked around a bit but could only find vague references to CINT, and it wasn't even clear to me whether a full CINT backend really existed or it was just a hack/experiment. Is it actually suitable for general-purpose use? If so, I'd certainly be happy to try it.. how would one go about swit

Re: [pypy-dev] cppyy and callbacks

On Fri, Jan 10, 2014 at 1:58 AM, Alex Stewart wrote: > I'd looked around a bit but could only find vague references to CINT, and it > wasn't even clear to me whether a full CINT backend really existed or it was > just a hack/experiment. Is it actually suitable for general-purpose use? > > If so,