On Sun, 26 Aug 2012 21:11:50 +0200, mathias.b...@gmx.de wrote:
> On 26.08.2012, 18:15:55 Phil Thompson wrote:
>> On Wed, 15 Aug 2012 11:55:47 +0200, mathias.b...@gmx.de wrote:
>>> On 15.08.2012, 11:05:42 Phil Thompson wrote:
I could change sipTransferTo() to do this if the owner was Py_None.
A
On 26.08.2012, 16:07:52 Phil Thompson wrote:
> On Sun, 26 Aug 2012 14:30:32 +0200, mathias.b...@gmx.de wrote:
>> On 26.08.2012, 16:46:24 Phil Thompson wrote:
>>> On Wed, 15 Aug 2012 15:54:11 +0200, mathias.b...@gmx.de wrote:
...
> Should all be fixed in current hg and tonight's snapshot.
> T
On 26.08.2012, 18:15:55 Phil Thompson wrote:
> On Wed, 15 Aug 2012 11:55:47 +0200, mathias.b...@gmx.de wrote:
>> On 15.08.2012, 11:05:42 Phil Thompson wrote:
>>> I could change sipTransferTo() to do this if the owner was Py_None. At
>>> the
>>> moment this is undocumented behaviour. Would this be s
On Sun, 26 Aug 2012 14:30:32 +0200, mathias.b...@gmx.de wrote:
> On 26.08.2012, 16:46:24 Phil Thompson wrote:
>> On Wed, 15 Aug 2012 15:54:11 +0200, mathias.b...@gmx.de wrote:
>>> Phil,
>>>
>>> sip can already propagate C++ exceptions into Python in cases
>>> where Python calls a C++ function whic
On 26.08.2012, 16:46:24 Phil Thompson wrote:
> On Wed, 15 Aug 2012 15:54:11 +0200, mathias.b...@gmx.de wrote:
>> Phil,
>>
>> sip can already propagate C++ exceptions into Python in cases
>> where Python calls a C++ function which throws an exception.
>>
>> However, if I extend a C++ class in Pyth