Skip to content

Invalid numbers parsed #22

@eleumik

Description

@eleumik

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

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)

See same issue for genson owlike/genson#111

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions