Heath Stewart

Is another release planned anytime soon including this change? It's been over a year since the last release was published to GitHub, at least, which is the same version as...

I appreciate that, but for those of us using package managers e.g., homebrew, new binaries haven't been released in over a year:  Are binary releases no longer recommended? Should...

The fix was recently released in 3.11.1: https://docs.python.org/release/3.11.1/whatsnew/changelog.html#python-3-11-1 However, testing the unchanged source against 3.11.1 doesn't work as expected. This work around may still be needed.

Looks like this is a bug that was just recently fixed in Python (for 3.12, alas): https://github.com/python/cpython/issues/96192, though there is a bot-created port for 3.11 that vim9 needs: https://github.com/python/cpython/pull/99455

Whoops. Forgot we decided to do this as a new parameter: `--paginate-all`, IIRC. I'll fix that before I finalize this PR, but figured it still shows how the go-gh work...

The eventual goal after talking with @andyfeller was to deprecate `--paginate-all` and bake this into `--paginate`. By rebasing onto trunk and merging - without squashing commits - the changes needed...

@williammartin I ran into an issue when porting some of my old tests from #5652 that would be better served by bifurcating the logic. I will try to work around...

Given further discussions about stability, @andyfeller @williammartin do we still want to add `--paginate-all`? I'm working on the changes now, and it certainly increases the complexity of several conditions. It's...

`--paginate` and `--paginate-all` are mutually exclusive. That means all errors when you specified `--paginate` e.g., with `--input` have to be updated to mention both of them. For code maintenance, in...

> might be broken by changing --paginate to work like --paginate-all Possibly, but that seems incredibly unlikely. The CLI would emit multiple pages like so: ```json { "data": { "viewer":...