Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Numbers parsed #111

Open
eleumik opened this issue Mar 23, 2017 · 0 comments
Open

Invalid Numbers parsed #111

eleumik opened this issue Mar 23, 2017 · 0 comments

Comments

@eleumik
Copy link

eleumik commented Mar 23, 2017

The following invalid Json numbers are parsed as numbers by genson:

034 parsed as 34, instead is invalid JSON, some other implementations parse it as an octal 28 that is what javascript would do. Same for -034. See http://stackoverflow.com/a/27361596/1536382

0., invalid for JSON, parsed as 0 like javascript would do, note that .0 is treated as an error (also invalid for JSON while for js is also ok), so for consistency also 0. should be, IMHO. If there is a way of doing relaxed-parsing may be both should be allowed in that case.

See also http://deron.meranda.us/python/comparing_json_modules/numbers#t5-3 (today unavailable, cached)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant