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

Switch to jq.py v1.7.0 #526

Merged
merged 3 commits into from
Jun 1, 2024
Merged

Switch to jq.py v1.7.0 #526

merged 3 commits into from
Jun 1, 2024

Conversation

spbnick
Copy link
Collaborator

@spbnick spbnick commented May 31, 2024

Switch to the v1.7.0.post1 version of our fork of jq.py, based on the upstream v1.7.0 release.

That release supports Python 3.12, and uses a newer release of jq, one where it's now necessary to explicitly request support for parsing RS-separated JSON (matching RFC 7464 and "application/json-seq" media type). So replace the --seq command-line option with two: --seq-in and --seq-out enabling RS separation in the input and the output respectively (but keep --seq as an alias for the latter).

Switch to the v1.7.0.post1 version of our fork of jq.py, based on the
upstream v1.7.0 release.

That release supports Python 3.12, and uses a newer release of jq, one
where it's now necessary to explicitly request support for parsing
RS-separated JSON (matching RFC 7464 and "application/json-seq" media
type). So replace the `--seq` command-line option with two: `--seq-in`
and `--seq-out` enabling RS separation in the input and the output
respectively (but keep `--seq` as an alias for the latter).
@spbnick spbnick merged commit cf260b7 into main Jun 1, 2024
6 checks passed
@spbnick spbnick deleted the switch_to_jq_py_1_7_0 branch June 1, 2024 05:24
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

Successfully merging this pull request may close these issues.

None yet

1 participant