Ah, I see that it did indeed get into 2.7: https://bitbucket.org/stackless-dev/stackless/commits/949c518c67c75a1655097a3f03e0a57f308a454a
On 7 October 2015 at 09:27, Kristján Valur Jónsson <swesk...@gmail.com> wrote: > Hi Robert. > Wow, it's been a long time since I tried using the boost_python wrappers. > It is likely that a lot of code is in there that does all kinds of magic. > Is it possible that you are running into the same kind of problem that we > had with other C python libraries that extend the basic PyObject? > > In february 2014 I checked in a fix to the way the PyHeapType object was > being used by stackless, see > https://bitbucket.org/stackless-dev/stackless/commits/0f781d2f > > As far as I can see, this never went into 2,.7 > Basically, the PyHeapType as used by stacklesspython deviates from the one > in regular Python. C extensions that add their own extensions to it, like > windowing extensions and presumably boost-python, will run into conflicts > with stackless internals. > > Can you check with recent versions of python 3? > > On 25 September 2015 at 16:13, Robert Babiak <rbab...@gmail.com> wrote: > >> I have posted a question over on stack overflow. One guy has commented >> that my code works for him. He didn't say he used stackless, so it is >> possible that this is something that might only occurs with stackless. If >> any of you have a moment to check out the question and chime in, I would be >> grateful. >> >> In short what I am seeing is if my derived class is returned (as a >> pointer to the base class) from the factory function to python then I get a >> segmentation fault. Python reports that the returned object is of the class >> that the factory produced (derived class) but attempts to access the >> derived classes methods causes the seg fault, but accessing the base class >> methods works. >> >> *Another question, is anyone aware of an issue with exposing polymorphic >> classes via a factory in an embedded stackless environment? * >> >> Factory returning boost exposed python object seg faults >> http://stackoverflow.com/q/32784954/2446566?sem=2 >> >> Thanks Robert. >> >> _______________________________________________ >> Stackless mailing list >> Stackless@stackless.com >> http://www.stackless.com/mailman/listinfo/stackless >> > >
_______________________________________________ Stackless mailing list Stackless@stackless.com http://www.stackless.com/mailman/listinfo/stackless
