There are several recent question on Stackoverflow about SystemError: new style getargs format but argument is not a tuple PIL/pillow, 2.7, Nov 28, 2016 https://stackoverflow.com/questions/40844212/systemerror-new-style-getargs-format-but-argument-is-not-a-tuple-even-the-argum ImageDraw.draw.line(), python, Sep 14, 2016 https://stackoverflow.com/questions/39497458/imagedraw-draw-line-systemerror-new-style-getargs-format-but-argument-is-no?rq=1 opencv, cv2.line, python, Sep 19, 2016 https://stackoverflow.com/questions/32673359/systemerror-new-style-getargs-format-but-argument-is-not-a-tuple?rq=1 opencv, cv2.imread/show, python, Nov 5, 2016 https://stackoverflow.com/questions/13225525/system-error-new-style-getargs-format-but-argument-is-not-a-tuple-when-using?rq=1 (code mostly from doc) ??.imread?, python, Jan 1, 2017 https://stackoverflow.com/questions/41419688/systemerror-new-style-getargs-format-but-argument-is-not-a-tuple-it-is-a-tup (and maybe others) [Would that people would identify OS and exact version of both python and imported module ;-)] No one commenting has a clue. Is message from Victor's new calling code? Was it backported to 2.7? Could error be a result of running old 3rd party binary that needs to be recompiled? -- Terry Jan Reedy
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4