Never mind about Py_fopen, I see you gave me a workaround.
On 8/4/17, 1:18 PM, "David Callahan" <[email protected]> wrote:
Wow, this is a 7-year old issue with boost;
https://svn.boost.org/trac10/ticket/4125 (
On 8/4/17, 12:55 PM, "David Callahan" <[email protected]> wrote:
Thanks. Did you look into the missing Py_fopen as well?
To answer your question, Facebook has a large python application which
leverages an even larger C++ code base which is exposed to python with iva
sadly large number of different ways including Boost. We are interested in
using PyPy but need to work through a bunch of these issues to even evaluate.
--david
On 8/4/17, 11:30 AM, "[email protected]" <[email protected]> wrote:
David,
since I didn't see a reply, I'm having a stab at it ...
There is patch file for wrapper.cpp:
pypy/module/cpyext/patches/boost.patch
which looks to be what you want, as it modifies the 'offending'
code. I've
not tested it.
And out of curiosity, why boost? cpyext needs to do a mapping of
internal
representations, which can be costly, and boost.python isn't known
for
speed either?
Best regards,
Wim
--
[email protected] -- +1 (510) 486 6411 --
www.lavrijsen.net
_______________________________________________
pypy-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-dev
