Phil, can you please confirm whether you will implement any such debugging aids in the SIP API (I take it there is nothing at the moment)? I could really use some introspection abilities into SIP when things don't work as expected, as happens from time to time. This should save me a lot of frustration ..<div>
<br></div><div>Arve<br><br><div class="gmail_quote">On Tue, Jul 28, 2009 at 4:53 PM, Arve Knudsen <span dir="ltr"><<a href="mailto:arve.knudsen@gmail.com">arve.knudsen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I can confirm that the reason was a build inconsistency (wrong version SIP header being included). As such, some debugging help from SIP could probably have saved me some time (and next time something like this happens). For instance, maybe one could adjust SIP's loglevel so it would output error messages when an incompatible PyQt is loaded (or whatever goes wrong here).<br>
<font color="#888888">
<br>Arve</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Tue, Jul 28, 2009 at 4:17 PM, Arve Knudsen <span dir="ltr"><<a href="mailto:arve.knudsen@gmail.com" target="_blank">arve.knudsen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div><div></div><div>On Tue, Jul 28, 2009 at 4:12 PM, Phil Thompson <span dir="ltr"><<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>></span> wrote:<br></div></div>
<div class="gmail_quote"><div><div></div><div><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
On Tue, 28 Jul 2009 16:03:05 +0200, Arve Knudsen <<a href="mailto:arve.knudsen@gmail.com" target="_blank">arve.knudsen@gmail.com</a>><br>
<div><div></div><div>wrote:<br>
> On Tue, Jul 28, 2009 at 3:53 PM, Phil Thompson<br>
> <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>>wrote:<br>
><br>
>> On Tue, 28 Jul 2009 15:38:09 +0200, Arve Knudsen<br>
<<a href="mailto:arve.knudsen@gmail.com" target="_blank">arve.knudsen@gmail.com</a>><br>
>> wrote:<br>
>> > Hi<br>
>> ><br>
>> > Are there any good troubleshooting techniques when unable to get a<br>
type<br>
>> > definition from the SIP API? Sometimes, when there are inconsistencies<br>
>> > in<br>
>> > my<br>
>> > build I am unable to get the type definition for QWidget, and I waste<br>
a<br>
>> lot<br>
>> > of time trying to find out what's gone wrong. If SIP itself could give<br>
>> > me<br>
>> > some useful info wrt. to its state, I'm sure that could save me a<br>
great<br>
>> > deal<br>
>> > of time.<br>
>><br>
>> I don't know what you mean by its state.<br>
>><br>
>> QWidget's type definition is a static data structure - sipType_QWidget.<br>
>> You<br>
>> don't get it, you just reference it.<br>
><br>
><br>
> This is from an application embedding Python, so I'm calling SIP's C API.<br>
> In this case I have no choice but to go via the API right?<br>
<br>
</div></div>Right.<br>
<div><br>
> What I do is<br>
> call<br>
> api_find_type("QWidget"), which in this case returns NULL.<br>
<br>
</div>I would think the most likely thing in that case is that the QtGui module<br>
hasn't been imported.</blockquote></div></div><div><br>It has been imported, and like I said this code works for certain builds. It is indicative of inconsistent builds that it doesn't work, and it would be great to have some debugging aids.<br>
<br>Arve <br></div></div><br>
</blockquote></div><br>
</div></div></blockquote></div><br></div>