> AFAIK that error in Python normally only happens in string formatting,
> i.e.:
>
>>>> "%d" % "a"
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> TypeError: int argument required
Agreed.
> I can reproduce the error by passing in the bug id as a string, i.e.
>
>>>> server.launchpad.set_launchpad_bug("1", 123)
> *** Fault: <Fault 2: "'int argument required' while executing 'launchpad.set_launchpad_bug()'">
>
What's odd is that at this point I haven't seen any other instances of this.
> Do your OOPSes save locals with types to know if that's the cause?
Irritatingly, not in the level of detail that's needed
However, what's confusing here is that I'm testing using the same code
that production Launchpad uses for other bug trackers. I haven't seen
any other instance of the error in the log so far, but I'll go back
and check to make sure it's not something common.
> AFAIK that error in Python normally only happens in string formatting,
> i.e.:
>
>>>> "%d" % "a"
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> TypeError: int argument required
Agreed.
> I can reproduce the error by passing in the bug id as a string, i.e. launchpad. set_launchpad_ bug("1" , 123) set_launchpad_ bug()'" >
>
>>>> server.
> *** Fault: <Fault 2: "'int argument required' while executing 'launchpad.
>
What's odd is that at this point I haven't seen any other instances of this.
> Do your OOPSes save locals with types to know if that's the cause?
Irritatingly, not in the level of detail that's needed
However, what's confusing here is that I'm testing using the same code
that production Launchpad uses for other bug trackers. I haven't seen
any other instance of the error in the log so far, but I'll go back
and check to make sure it's not something common.