WELL, I figured it out--thanks to everyone's help. There were instances
of the object and I am a total moron.
Thanks again to everyone who helped me stomp this out. :)
On Wed, 2005-10-05 at 21:58 -0400, Jeremy Moles wrote:
> So, here is my relevant code:
>
> PyArg_ParseTuple(args, "O!", &P
[Jeremy Moles]
> ...
> I may be missing something critical here, but I don't exactly grok what
> you're saying; how is it even possible to have two instances of
> PyType_vector3d? It is (like all the examples show and all the extension
> modules I've done in the past) a static structure declared an
Well, there's certainly no doubting that all of you are right. I guess
now I need to track down how this is happening and either fix it or
understand it so that I can explain why I'm having to work around it. :)
Many, many thanks. :)
On Thu, 2005-10-06 at 16:48 +0200, Daniel Dittmar wrote:
> Jere
Jeremy Moles wrote:
> So, here is my relevant code:
>
> PyArg_ParseTuple(args, "O!", &PyType_vector3d, &arg1)
>
> And here ismy error message:
>
> argument 1 must be pylf.core.vector3d, not pylf.core.vector3d
try adding
printf("%p %p\n", &PyType_vector3d, arg1->ob_type);
before the parsetup
Jeremy Moles wrote:
> So, here is my relevant code:
>
> PyArg_ParseTuple(args, "O!", &PyType_vector3d, &arg1)
>
> And here ismy error message:
>
> argument 1 must be pylf.core.vector3d, not pylf.core.vector3d
>
It looks as if two PyType_vector3d exist in your system
- the one that
Jeremy Moles <[EMAIL PROTECTED]> writes:
> Thanks for the reply. :)
>
> I may be missing something critical here, but I don't exactly grok what
> you're saying; how is it even possible to have two instances of
> PyType_vector3d? It is (like all the examples show and all the extension
> modules I'v
Thanks for the reply. :)
I may be missing something critical here, but I don't exactly grok what
you're saying; how is it even possible to have two instances of
PyType_vector3d? It is (like all the examples show and all the extension
modules I've done in the past) a static structure declared and a
Jeremy Moles <[EMAIL PROTECTED]> writes:
> So, here is my relevant code:
>
> PyArg_ParseTuple(args, "O!", &PyType_vector3d, &arg1)
>
> And here ismy error message:
>
> argument 1 must be pylf.core.vector3d, not pylf.core.vector3d
>
> I know PyType_vector3d "works" (as I can use them in
All of these are runtime errors. Using GCC4 and compiling perfectly with
-Wall.
On Thu, 2005-10-06 at 09:12 -0500, Brandon K wrote:
> > If I take out the "!" in the format string and just use "O", I can at
> > least get past PyArg_ParseTuple.
>
> Is this a compile-time error? Or a runtime error?
> If I take out the "!" in the format string and just use "O", I can at
> least get past PyArg_ParseTuple.
Is this a compile-time error? Or a runtime error?
== Posted via Newsgroups.com - Usenet Access to over 100,000 Newsgroups
==
Get Anonymous, Uncensored, Access to West and East C
So, here is my relevant code:
PyArg_ParseTuple(args, "O!", &PyType_vector3d, &arg1)
And here ismy error message:
argument 1 must be pylf.core.vector3d, not pylf.core.vector3d
I know PyType_vector3d "works" (as I can use them in the interpreter all
day long), and I know I'm passi
11 matches
Mail list logo
