Recent changes to 1: TypeError str returned non-string

#1 TypeError str returned non-string

Ilya Etingof — Sat, 14 Mar 2015 10:59:27 -0000

So far I can't confirm that the exception is indeed bubbled up from pyasn1 internals. Could you please perform some more investigation to figure out what is the class of the problem exception object?

I'd suggest [recursively] trying thinks like:

import inspect
inspect.getsource(e.class)

As well as:

e.str()
...
dir(a)
...
e.args
...
[ inspect.getsource(x.class) for x in e.args ]
...
[ (x.class, x.str()) for x in e.args ]

I suspect that the SSLError exception (from requests module) was instantiated with objects of some other class (should be in e.args) which in turn may be instantiated by some other objects. Some of these may have faulty str() implementation.

#1 TypeError str returned non-string

Andres Riancho — Wed, 11 Mar 2015 20:04:54 -0000

PS: I tried to debug it myself by looking at the code and trying to find any place where there could be a monkey-patch... but failed to find it.

TypeError str returned non-string

Andres Riancho — Tue, 10 Mar 2015 17:08:24 -0000

Seen the str bug that seems to be in pyasn1? Its affecting requests and other tools such as mine (w3af).

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766481
https://github.com/andresriancho/w3af/issues/8715

Recent changes to 1: TypeError __str__ returned non-string

#1 TypeError __str__ returned non-string

#1 TypeError __str__ returned non-string

TypeError __str__ returned non-string

Recent changes to 1: TypeError str returned non-string

#1 TypeError str returned non-string

#1 TypeError str returned non-string

TypeError str returned non-string