Mixing
literal_eval incorrectly parsing ints
3
I am trying to use the ast.literal_eval function to parse a dictionary string into a dictionary. The issue I am having is that the function is incorrectly evaluating integers of the form 0420 as 272. Is there a better way to do this?
Example:
String:
{"neurons": [80, 140, 84, 5], "epochs": 0420}
Output
{'epochs': 272, 'neurons': [80, 140, 84, 5]}
python dictionary
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
add a comment |
3
I am trying to use the ast.literal_eval function to parse a dictionary string into a dictionary. The issue I am having is that the function is incorrectly evaluating integers of the form 0420 as 272. Is there a better way to do this?
Example:
String:
{"neurons": [80, 140, 84, 5], "epochs": 0420}
Output
{'epochs': 272, 'neurons': [80, 140, 84, 5]}
python dictionary
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
5
That's not incorrect parsing; in Python 2.x, numeric literals starting with a zero are octal (in 3.x, they're a syntax error). Where is this data coming from? What did you expect instead ("0420"?420?)
– jonrsharpe
Nov 21 '18 at 15:16
1
That's my bad. Yes I expected to get 420 in this case. Is there a way to do this effectively?
– Euclidean
Nov 21 '18 at 15:25
2
You could parse it yourself, or pre-process the string to remove those leading zeros.
– jonrsharpe
Nov 21 '18 at 15:26
add a comment |
3
3
3
I am trying to use the ast.literal_eval function to parse a dictionary string into a dictionary. The issue I am having is that the function is incorrectly evaluating integers of the form 0420 as 272. Is there a better way to do this?
Example:
String:
{"neurons": [80, 140, 84, 5], "epochs": 0420}
Output
{'epochs': 272, 'neurons': [80, 140, 84, 5]}
python dictionary
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
I am trying to use the ast.literal_eval function to parse a dictionary string into a dictionary. The issue I am having is that the function is incorrectly evaluating integers of the form 0420 as 272. Is there a better way to do this?
Example:
String:
{"neurons": [80, 140, 84, 5], "epochs": 0420}
Output
{'epochs': 272, 'neurons': [80, 140, 84, 5]}
python dictionary
python dictionary
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
edited Nov 21 '18 at 15:18
jonrsharpe
77.7k11104212
77.7k11104212
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
asked Nov 21 '18 at 15:13
EuclideanEuclidean
1304
1304
5
That's not incorrect parsing; in Python 2.x, numeric literals starting with a zero are octal (in 3.x, they're a syntax error). Where is this data coming from? What did you expect instead ("0420"?420?)
– jonrsharpe
Nov 21 '18 at 15:16
1
That's my bad. Yes I expected to get 420 in this case. Is there a way to do this effectively?
– Euclidean
Nov 21 '18 at 15:25
2
You could parse it yourself, or pre-process the string to remove those leading zeros.
– jonrsharpe
Nov 21 '18 at 15:26
add a comment |
5
That's not incorrect parsing; in Python 2.x, numeric literals starting with a zero are octal (in 3.x, they're a syntax error). Where is this data coming from? What did you expect instead ("0420"?420?)
– jonrsharpe
Nov 21 '18 at 15:16
1
That's my bad. Yes I expected to get 420 in this case. Is there a way to do this effectively?
– Euclidean
Nov 21 '18 at 15:25
2
You could parse it yourself, or pre-process the string to remove those leading zeros.
– jonrsharpe
Nov 21 '18 at 15:26
5
5
That's not incorrect parsing; in Python 2.x, numeric literals starting with a zero are octal (in 3.x, they're a syntax error). Where is this data coming from? What did you expect instead (
"0420"? 420?)– jonrsharpe
Nov 21 '18 at 15:16
That's not incorrect parsing; in Python 2.x, numeric literals starting with a zero are octal (in 3.x, they're a syntax error). Where is this data coming from? What did you expect instead (
"0420"? 420?)– jonrsharpe
Nov 21 '18 at 15:16
1
1
That's my bad. Yes I expected to get 420 in this case. Is there a way to do this effectively?
– Euclidean
Nov 21 '18 at 15:25
That's my bad. Yes I expected to get 420 in this case. Is there a way to do this effectively?
– Euclidean
Nov 21 '18 at 15:25
2
2
You could parse it yourself, or pre-process the string to remove those leading zeros.
– jonrsharpe
Nov 21 '18 at 15:26
You could parse it yourself, or pre-process the string to remove those leading zeros.
– jonrsharpe
Nov 21 '18 at 15:26
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53415085%2fliteral-eval-incorrectly-parsing-ints%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53415085%2fliteral-eval-incorrectly-parsing-ints%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
5
That's not incorrect parsing; in Python 2.x, numeric literals starting with a zero are octal (in 3.x, they're a syntax error). Where is this data coming from? What did you expect instead (
"0420"?420?)– jonrsharpe
Nov 21 '18 at 15:16
1
That's my bad. Yes I expected to get 420 in this case. Is there a way to do this effectively?
– Euclidean
Nov 21 '18 at 15:25
2
You could parse it yourself, or pre-process the string to remove those leading zeros.
– jonrsharpe
Nov 21 '18 at 15:26