[creditdunord] Encoding issue compatibility python 2/3
when weboob was lauched by python 3, the accounts' id was containing bytestring (eg : 123456789b'0'b'1' instead of 12345678901) this created a new account and deleted the older one so when the client wanted to access/actived it, he had an error then we switched the client on his new account in the backend, but the problem occured again when it forced a synchronisation The automatic sync and the forced one do not use the same python version this issue came from the use of : weboob.tools.compat.unicode(my_str).encode('utf-8') resolved by : weboob.tools.misc.to_unicode(my_str)
Please register or sign in to comment