added option to convert dictionary values from strings #262
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
|
I've made fixes to pass the code on Travis. It is currently passing all environments except Jython. It looks like the error is unrelated to these changes (https://travis-ci.com/github/martinblech/xmltodict/jobs/428438169). Could you take a look and confirm? |
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.
Added code to interpret strings in the dictionary value field to be interpreted as Python values (int, float, bool, etc). Default behavior remains unchanged, this additional step only occurs if
convert_values=Truein theparsefunction.An example has been added to the
parsedocstring and to the list of unit tests.PR is set as draft since I could not run tox on my local machine. I'll wait for Travis to run the tests and convert from draft to full PR once it's passing.