Closed kil closed 7 years ago
Thanks for reporting this!
This is basically a design flaw of suds-jurko (0.6.0), the development branch of suds-jurko 0.7.0 has fixed this problem, you can read the change log here https://bitbucket.org/jurko/suds, before the suds-jurko 0.7.0 release, We can first take a work around for this problem, and give a solution for this problem in the next release of bingads.
Thank you for looking into this, i would really appreciate it if you guys could provide a work around until when or if there is an update to suds-jurko.
currently no plan to fix it. close issue. Thanks.
This is causing issues on our production systems. We spawn a reasonable amount of processes that require this library and the amount of stuff that is being written to disk just by importing ServiceClient
is ridiculous, especially as there is no easy way to disable this behavior.
Please reconsider fixing this.
Ugly workaround for people getting to this issue (only use if you never require any caching)
import suds.cache
class UglyNoCache(suds.cache.NoCache):
def __init__(self, location=None, **duration):
print("Ugly hack to monkeypatch bing ads's import defaults")
suds.cache.ObjectCache = UglyNoCache
Thanks @duijf !
The suds client instantiated at https://github.com/bing-ads-sdk/BingAds-Python-SDK/blob/master/bingads/service_client.py#L250-L252 uses the default suds caching strategy and file location (thats
/tmp/suds
, where the/tmp
part comes fromgettempdir()
).That means if two users run this test program:
the one that comes second will see this error:
Would be great if that was configurable (eg. if it was possible to provide the
cache
argument to the suds client).