Clay Gerrard added the comment:
I don't think the default is bad/wrong so much as it's an inflexible magic
number.
I think blocksize should be parameterized as an attribute on the connection -
or at least a class attribute or module level constant so we can monkey patch
it without
Clay Gerrard added the comment:
and for *encoding* case? Can you just add the encoding argument back to
json.dumps? Have it default to None because of backwards compatibility in
python3 and continue to return strings by default...
... and then *everyone* that ever wants to *serialize* an
Clay Gerrard added the comment:
BUMP. ;)
This issue was recently raised as one blocker to OpenStack Object Storage
(Swift) finishing our port to python3 (we're hoping to finish adding support
>=3.5 by Spring '17 - /me crosses fingers).
I wonder if someone might confirm or deny