Hi Helmut, On Sat, 9 Jun 2018 15:16:40 +0200 Helmut Grohne <hel...@subdivi.de> wrote: > I got the error "unexpected crash: name 'basestring' is not defined" from the > hoogle backend. I guess this is due to searx.utils.to_string using basestring > without defining it. Regardless of whether that's the cause, the use of > basestring in to_string is certainly a bug.
I don't know which code exactly threw that error but. - the hoogle backend is now provided by the json_engine engine which does not reference basestring at all - all other references to basestring in the codebase seem to be set as str. Can you confirm that the issue is solved with the upload of the new upstream release 0.15.0? Thanks! cheers, josch
signature.asc
Description: signature
