estimate_keyword_traffic.py example throws error regarding suds

[AiDinho]

I am running the example script and its running fine and showing result ,but along the way it throws a bunch of error .
ERROR:suds.resolver:(Money) not-found
ERROR:suds.resolver:path: "Money", not-found
ERROR:suds.resolver:(Keyword) not-found
ERROR:suds.resolver:path: "Keyword", not-found
ERROR:suds.resolver:(Keyword) not-found
ERROR:suds.resolver:path: "Keyword", not-found
ERROR:suds.resolver:(Keyword) not-found
ERROR:suds.resolver:path: "Keyword", not-found
ERROR:suds.resolver:(Keyword) not-found
ERROR:suds.resolver:path: "Keyword", not-found
ERROR:suds.resolver:(Location) not-found
ERROR:suds.resolver:path: "Location", not-found
ERROR:suds.resolver:(Language) not-found
ERROR:suds.resolver:path: "Language", not-found

could someone enlighten on how to fix these errors or this are something that I can ignore ,
I am using a test account at the moment .

[junna-zhou]

the same problem, have you solve it ?

[parander]

Duplicate of #35 #41

I think you can ignore the error because the function seems to work as expected even though it prints all these errors. But your logs will of course get cluttered so the best would be if the error was "fixed" (i.e. removed if it's not really an error)

[msaniscalchi]

I'm surprised that this has come up again. As mentioned in the previous comment, this is a duplicate of a re-opened issue, so I'll be closing this.

Even when it occurred last time, it was more of a cosmetic error logged by suds; the API call would otherwise work as intended. Until I get some time to look into this, it might make sense to temporarily disable the suds.resolver logger if this is flooding your logs.

[junna-zhou]

ok, i see.
thanks for your answers.
the API works fine, so I will disable the logger for suds.resolver.