This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yellalena
Recipients xtreak, yellalena
Date 2020-08-29.14:45:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1598712316.14.0.556973835668.issue41658@roundup.psfhosted.org>
In-reply-to
Content
hi Karthikeyan Singaravelan!
I'm working with a russian database called 1C. it's pretty popular here in Russia, and its 'twist' is that everything there (I mean code) is written in Russian, i.e. cyrillic. So it's obvious and normal that the request/response coming from 1C base could contain non-ascii characters in its parts. Particularly, my case was that the header has a header containing info on called method, which value was "http://www.1c-bitrix.ru#SVD_ВебСервис:GetEmployee". which causes the "'latin-1' codec cant encode characters in position 29-37: ordinal not in range(256)" exception every time I try to send a request there. I tested locally, and same happening if I'm trying to add a Cyrillic header when creating a request/response in Python.
History
Date User Action Args
2020-08-29 14:45:16yellalenasetrecipients: + yellalena, xtreak
2020-08-29 14:45:16yellalenasetmessageid: <1598712316.14.0.556973835668.issue41658@roundup.psfhosted.org>
2020-08-29 14:45:16yellalenalinkissue41658 messages
2020-08-29 14:45:16yellalenacreate