Remove newline characters from JSON #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some cases (did not figure out when and when not), toJSON leads to representations like
> toJSON(x_2)
[1] "[ [\n \"Scenario\",\n\"Waterbody\", ....
instead of
> toJSON(x_1)
[1] "[ [ \"Scenario\", \"Waterbody\", ...
which makes python.assign fail with the message
SyntaxError: EOL while scanning string literal
This can be avoided by substituting the newline characters in the JSON string before it is passed to the Python interpreter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks for this nice package!
In some cases (did not figure out when and when not), toJSON leads to representations like
instead of
which makes python.assign fail with the message
This can be avoided by substituting the newline characters in the JSON string before it is passed to the Python interpreter.
I am not clear what the difference between the code in this github project and the r-forge project is, this also applies to the code on r-forge. I only submitted the fix here, as it is easier on github.