python-json5-0.9.4-bp156.3.1

- update to 0.12.0
  * jump several versions with meta/test changes
  * from 0.11.0:
  * Fix a typing issue in dump and dumps with the cls argument
  * Introduce a new parse method
  * Fix #60 - parsing '--6.0' incorrectly
  * from 0.10.1:
  * Add custom encoding to dump/dumps

- update to 0.9.28:
  * Fix GitHub CI to install uv so ./run tests works properly.
  * Mark Python3.13 as supported in package metadata.
  * Update dev package dependencies
  * Fix typo in //README.md
  * GitHub issue #82 Add support for the strict parameter to
    load()/loads().
  * Significantly rework the infra and the run script to be
    contemporary.

- update to 0.9.25:
  * Explicitly specify the directory to use for the package in
    pyproject.toml.

- update to 0.9.24:
  * drop python2
  * switch to pyproject.toml
  * add typing
  * format with ruff

- update to 0.9.14:
  * Handle `+Infinity` as well as `-Infinity` and `Infinity`.

- update to 0.9.13:
  * Remove a field from one of the JSON benchmark files to
    reduce confusion in Chromium.
  * No code changes.

- update to 0.9.12:
  * fix dump error on python 2
  * fix GitHub actions

- update to 0.9.10:
  * Updated the //README.md to be clear that parsing arbitrary JS
    code may not work.
  * Fixed serialization for objects that subclass `int` or `float`:
    Previously we would use the objects __str__ implementation, but
    that might result in an illegal JSON5 value if the object had
    customized __str__ to return something illegal. Instead,
    we follow the lead of the `JSON` module and call `int.__repr__`
    or `float.__repr__` directly.
  * While I was at it, I added tests for dumps(-inf) and dumps(nan)
    when those were supposed to be disallowed by `allow_nan=False`.

- update to 0.9.8:
  * Fixed error reporting in some cases due to how parsing was handling
    nested rules in the grammar - previously the reported location for
    the error could be far away from the point where it actually happened.
  * Fixed behavior of `default` fn in `dump` and `dumps`. Previously
    we didn't require the function to return a string, and so we could
    end up returning something that wasn't actually valid. This change
    now matches the behavior in the `json` module.

- Added BuildRequires:  alts

- %python3_only -> %python_alternative

- version update to 0.9.4
  * v0.9.4 (2020-03-26)
  * [GitHub pull #38](https://github.com/dpranke/pyjson5/pull/38)
    Fix from fredrik@fornwall.net for dumps() crashing when passed
    an empty string as a key in an object.
  * v0.9.3 (2020-03-17)
  * [GitHub pull #35](https://github.com/dpranke/pyjson5/pull/35)
    Fix from pastelmind@ for dump() not passing the right args to dumps().
  * Fix from p.skouzos@novafutur.com to remove the tests directory from
    the setup call, making the package a bit smaller.
  * v0.9.2 (2020-03-02)
  * [GitHub pull #34](https://github.com/dpranke/pyjson5/pull/34)
    Fix from roosephu@ for a badly formatted nested list.
  * v0.9.1 (2020-02-09)
  * [GitHub issue #33](https://github.com/dpranke/pyjson5/issues/33):
    Fix stray trailing comma when dumping an object with an invalid key.
  * v0.9.0 (2020-01-30)
  * [GitHub issue #29](https://github.com/dpranke/pyjson5/issues/29):
    Fix an issue where objects keys that started with a reserved
    word were incorrectly quoted.
  * [GitHub issue #30](https://github.com/dpranke/pyjson5/issues/30):
    Fix an issue where dumps() incorrectly thought a data structure
    was cyclic in some cases.
  * [GitHub issue #32](https://github.com/dpranke/pyjson5/issues/32):
    Allow for non-string keys in dicts passed to ``dump()``/``dumps()``.
    Add an ``allow_duplicate_keys=False`` to prevent possible
    ill-formed JSON that might result.

- Initial version