Hi Alex,
By the way - the only reason i use C++ in my project is because I have a
massive amount of legacy code that uses several C libraries and Qt, as well as
openGL, so porting that bunch to python can be quite a hassle. The only
problem is that Python side has to send certain requests to C++
Well, as far as I can see from where I am, the only real good that can come
from interfacing with PyObject is the capability to write container classes in
C++. On the other hand, it seems that it is not very often needed. For the
case when objects just need to be LINKED from the C++ code as refe
Hi Wim,
On Tue, Jun 5, 2012 at 1:53 AM, wrote:
> Overall, I'm happy enough with the result (I'm going to need handling of
> PyObject*'s later for my own nefarious purposes).
Maybe we can motivate you to look for and fix inefficiencies in
cpyext :-) As far as I know it's still fully designed fo
Hi Amaury,
On Mon, Jun 4, 2012 at 10:32 PM, Amaury Forgeot d'Arc
wrote:
> Maybe we should retry with different pypy trees (i.e pypy/interpreter/ vs.
> pypy3k/interpreter/, and so on)
> But I'm sure we would like some objects to be compatible, for
> example PyFrame2.f_backref could be a PyFrame3.
