-
Notifications
You must be signed in to change notification settings - Fork 298
mhtml TypeError: 'unicode' object does not support item assignment #475
Comments
Confirming this behavior, with SleekXMPP 1.3.3 and Python 2.7.15 (current Debian Testing):
|
@ajparkerbis @LuccoJ: Always present for "master"? Have you a patch? |
Attached is a minimal example that triggers this issue, based on I don't have a patch for SleekXMPP, as this is my first time looking at its code (I'm debugging an issue in software written by somebody else that stopped working, probably between debian jessie (python-sleekxmpp 1.0~beta5) and stable/testing (python(3)-sleekxmpp 1.3.3)). I've checked the documentation at https://sleekxmpp.readthedocs.io/en/latest/api/basexmpp.html#sleekxmpp.basexmpp.BaseXMPP.send_message and it seems that the declared API hasn't changed, so this looks like a regression. |
We were moving a script from a server with version 1.3.1 of sleekxmpp to 1.3.3 and messages sent via mhtml with a space and then colon : caused a hang or broken parsing of mhtml.
Here is a code snippet:
sending most text to the fifo worked fine - sending Problem: even worked fine. It was Problem : that then caused a hang and prompted the TypeError
The error we see is:
TypeError: 'unicode' object does not support item assignment -
and it references the mhtml line.
(there's an elif for the other match and an else - everything was working properly with 1.3.1 and we resolved the issue by rolling the new server back to sleekxmpp 1.3.1 from 1.3.3)
*On CentOS 7.3.1611 with python 2.7.5 and sleekxmpp 1.3.3
The text was updated successfully, but these errors were encountered: