Message 318954 - Python tracker

➜

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	radsquirrel
Recipients	radsquirrel
Date	2018-06-07.16:32:41
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1528389161.29.0.592728768989.issue33797@psf.upfronthosting.co.za>
In-reply-to

Content
JSON does not correctly encode dbus.Byte from dbus-python on 2.7: dbus.Byte is a subclass of int with its own __str__ implementation. >>> import json >>> import dbus >>> json.dumps(dbus.Byte(0)) '\x00' On 3.x: >>> import json >>> import dbus >>> json.dumps(dbus.Byte(0)) '0' This seems to have been fixed in 3.x here: https://bugs.python.org/issue18264 and subsequently: https://bugs.python.org/issue26719 I'm interested in backporting these but they are marked as enhancements. However a backport for a similar issue: https://bugs.python.org/issue27934 was accepted. Would the maintainers be amenable to a backport of 18264 & 26719?

JSON does not correctly encode dbus.Byte from dbus-python on 2.7:

dbus.Byte is a subclass of int with its own __str__ implementation.

>>> import json
>>> import dbus
>>> json.dumps(dbus.Byte(0))
'\x00'

On 3.x:

>>> import json
>>> import dbus
>>> json.dumps(dbus.Byte(0))
'0'

This seems to have been fixed in 3.x here:
https://bugs.python.org/issue18264
and subsequently:
https://bugs.python.org/issue26719

I'm interested in backporting these but they are marked as enhancements.  However a backport for a similar issue:
https://bugs.python.org/issue27934

was accepted.  Would the maintainers be amenable to a backport of 18264 & 26719?

History
Date	User	Action	Args
2018-06-07 16:32:41	radsquirrel	set	recipients: + radsquirrel
2018-06-07 16:32:41	radsquirrel	set	messageid: <1528389161.29.0.592728768989.issue33797@psf.upfronthosting.co.za>
2018-06-07 16:32:41	radsquirrel	link	issue33797 messages
2018-06-07 16:32:41	radsquirrel	create