PEP 837: Extensible JSON serialization

Playing Devil’s advocate, adding copyreg.json will not introduce a global state? I don’t remember exactly where, but I remember that some core devs opposed to such an idea.

What if an extension X will register with copyreg a JSON serializer for a class, and another extension Y will register another serializer for the same class? Is there same bad precedent with copyreg.pickle usage in real world?