Message326761
IIRC, there was an early decision to handle only exact types and their subclasses (plus tuples). For example, os.environ and instances of collections.ChainMap are not JSON serializable.
I believe the reason was that it made encoding faster, more predictable, and more likely to match round-trip expectations. For those wanting more generality, there are at least two options. The simplest option is to coerce the input to supported type. A more complete solution is to write a subclass of JSONEncoder to pass into json.dump() as the *cls* argument (there are examples of how to do this in the docs).
For the specific case of mappingproxy, there is another issue. Multiple components of a class dict are not all JSON serializable, so you have the same problem yet again with getset_descriptor objects, member objects, and various slot wrappers. |
|
Date |
User |
Action |
Args |
2018-10-01 03:26:23 | rhettinger | set | recipients:
+ rhettinger, bob.ippolito, Michael Smith2 |
2018-10-01 03:26:23 | rhettinger | set | messageid: <1538364383.68.0.545547206417.issue34858@psf.upfronthosting.co.za> |
2018-10-01 03:26:23 | rhettinger | link | issue34858 messages |
2018-10-01 03:26:23 | rhettinger | create | |
|