Kill JsonIO and fix JSON driver caching issues #2796
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I admit I got a bit carried away and killed my least favourite module in all of Red!
This PR fixes #2793 with the solution described in my comment on that issue.
The reasons for killing JsonIO were mainly:
_threadsafe
methods were misleadingOther changes include:
deepcopy()
on all of a cog's data every time a JSON is saved (oof)pickle.loads(pickle.dumps())
overdeepcopy()
everywhere in Config and the JSON driver