Make the (interactive) output of run-install-tests much nicer.

Review Request #14876 — Created March 5, 2026 and updated

Information

rbinstall
master

Reviewers

Since we have the rich library available in the rbinstall context, we
might as well use it. This makes it so parallel builds display in a live
table.

This also adds a --list argument which will print a list of the
available build targets (in case we want to do something like add this
to CI later).

Ran install tests and saw much nicer output.

Summary ID
Make the (interactive) output of run-install-tests much nicer.
Since we have the `rich` library available in the rbinstall context, we might as well use it. This makes it so parallel builds display in a live table. This also adds a `--list` argument which will print a list of the available build targets (in case we want to do something like add this to CI later). Testing Done: Ran install tests and saw much nicer output.
wvypxystvwoszxtpxwuzwulylpptnyzr

Description From Last Updated

line too long (83 > 79 characters) Column: 80 Error code: E501

reviewbotreviewbot

Blank line here.

chipx86chipx86

I think these can be Mapping.

chipx86chipx86

Let's make this keyword-only.

chipx86chipx86

Missing a Version Added and a Version Changed above. I know it's tests, but it's still nice to have that …

chipx86chipx86

Let's make these keyword-only.

chipx86chipx86

Missing , optional. Also, same feedback about doc versioning.

chipx86chipx86

Can we make these keyword-only?

chipx86chipx86

This can be: for dist, dist_info in sorted(DISTS.items()):

chipx86chipx86

Seems we shouldn't even bother with the for loop is platforms_set is empty.

chipx86chipx86

Blank line here.

chipx86chipx86

This should use the standard multi-line format.

chipx86chipx86

Can we call this build?

chipx86chipx86

We generally do one keyword argument per line.

chipx86chipx86
Checks run (1 failed, 1 succeeded)
flake8 failed.
JSHint passed.

flake8

david
chipx86
  1. 
      
  2. tests/run-install-tests.py (Diff revision 2)
     
     
     
    Show all issues

    Blank line here.

  3. tests/run-install-tests.py (Diff revision 2)
     
     
     
     
     
    Show all issues

    I think these can be Mapping.

  4. tests/run-install-tests.py (Diff revision 2)
     
     
    Show all issues

    Let's make this keyword-only.

  5. tests/run-install-tests.py (Diff revision 2)
     
     
     
    Show all issues

    Missing a Version Added and a Version Changed above.

    I know it's tests, but it's still nice to have that information.

  6. tests/run-install-tests.py (Diff revision 2)
     
     
     
     
     
     
    Show all issues

    Let's make these keyword-only.

  7. tests/run-install-tests.py (Diff revision 2)
     
     
    Show all issues

    Missing , optional.

    Also, same feedback about doc versioning.

  8. tests/run-install-tests.py (Diff revision 2)
     
     
     
     
     
     
    Show all issues

    Can we make these keyword-only?

  9. tests/run-install-tests.py (Diff revision 2)
     
     
     
    Show all issues

    This can be:

    for dist, dist_info in sorted(DISTS.items()):
    
  10. tests/run-install-tests.py (Diff revision 2)
     
     
    Show all issues

    Seems we shouldn't even bother with the for loop is platforms_set is empty.

    1. I'll just have the entire thing error out, because that doesn't make sense.

  11. tests/run-install-tests.py (Diff revision 2)
     
     
     
    Show all issues

    Blank line here.

  12. tests/run-install-tests.py (Diff revision 2)
     
     
    Show all issues

    This should use the standard multi-line format.

  13. tests/run-install-tests.py (Diff revision 2)
     
     
    Show all issues

    Can we call this build?

  14. tests/run-install-tests.py (Diff revision 2)
     
     
    Show all issues

    We generally do one keyword argument per line.

  15. 
      
david
Review request changed
Commits:
Summary ID
Make the (interactive) output of run-install-tests much nicer.
Since we have the `rich` library available in the rbinstall context, we might as well use it. This makes it so parallel builds display in a live table. This also adds a `--list` argument which will print a list of the available build targets (in case we want to do something like add this to CI later). Testing Done: Ran install tests and saw much nicer output.
wvypxystvwoszxtpxwuzwulylpptnyzr
Make the (interactive) output of run-install-tests much nicer.
Since we have the `rich` library available in the rbinstall context, we might as well use it. This makes it so parallel builds display in a live table. This also adds a `--list` argument which will print a list of the available build targets (in case we want to do something like add this to CI later). Testing Done: Ran install tests and saw much nicer output.
wvypxystvwoszxtpxwuzwulylpptnyzr

Checks run (2 succeeded)

flake8 passed.
JSHint passed.