I was exploring the boost C++ library support for Python 3 extensions with Python3.5 using a built-from-source copy of pypy using the py3.5 branch. Below are the errors I encountered.
Are these expected problems that someone is working on?
Should someone be working on them?
Or is this intended behavior and I should adapt boost?
Thanks
--david
libs/python/src/exec.cpp: In function ‘boost::python::api::object boost::python::exec_file(boost::python::str, boost::python::api::object, boost::…
[View More]python::api::object)’:
libs/python/src/exec.cpp:89:30: error: ‘_Py_fopen’ was not declared in this scope
FILE *fs = _Py_fopen(f, "r");
^
libs/python/src/wrapper.cpp: In member function ‘boost::python::override boost::python::detail::wrapper_base::get\_override(const char*, PyTypeObject*) const’:
libs/python/src/wrapper.cpp:28:50: error: ‘struct PyMethodObject’ has no member named ‘im_self’
> && ((PyMethodObject*)m.get())->im_self == this->m_self
^
libs/python/src/wrapper.cpp:37:61: error: ‘struct PyMethodObject’ has no member named ‘im_func’
if (borrowed_f != ((PyMethodObject*)m.get())->im_func)
^
[View Less]
Hello,
our projects runs on python 3.4, and when trying to run them with pypy3
we run into this problem:
when trying to send bytearray with send()
like:
clientSocket.send(bytearray(some_bytes))
it fails on:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/opt/pypy3-v5.8.0-src/site-packages/zmq/backend/cffi/socket.py",
line 209, in send
c_message = ffi.new('char[]', message)
File "/opt/pypy3-v5.8.0-src/lib_pypy/cffi/api.py", line 250, in new
…
[View More]return self._backend.newp(cdecl, init)
TypeError: 'bytearray' object cannot be interpreted as an integer
it behaves differently when running with python3.4 (Cpython) - which works
i'm not sure if the problem is with the the pyzmq library or the cffi
thank you in advance
--
[View Less]
