python / python/cpython

Add tests for command-line interface

Aperta
#131,178 13 commenti 2 reazioni 1 assegnatario Vedi su GitHub

@donbarbos ci sta già lavorando.

Dal 13/3/2025.

easy tests type-feature
Lingua principale
Python
Stelle
77.2k
Fork
35.9k
Metriche di merge delle PR
Metriche PR in attesa

Descrizione

While working on #130160 and #93096 it was decided that it would be worth paying attention to the problem of lack of tests for command line interface.

List of all cli modules is in the documentation: https://docs.python.org/dev/library/cmdline.html

Many modules are missing command line interface tests, so I suggest using this issue to submit PRs for now only for well-documented interfaces, for example:

  • tokenize (gh-131274)
  • platform (gh-131542)
  • pickle (gh-131275)
  • ast (gh-133329)
  • pickletools (gh-131287)
  • http.server (gh-132540)
  • profile (gh-134103)
  • cProfile (gh-134269)
  • site (gh-133582)

TODO: Make sure all documented have tests for CLI (others are not so important as it has not been decided what to do with them yet)

You can use PR #127759 for dis module or #118132 for random module as a reference.
And I also suggest using subprocess.Popen to allocate a separate resource since some modules can block a lot of time.

[!IMPORTANT]
For those who want to work on the issue, please:

  • Select one module for which tests will be improved. It's easier to review and backport.
  • Open a pull request with the following title: gh-131178: Add tests for `MODULE_NAME` command-line interface
Linked PRs
  • gh-131274
  • gh-131275
  • gh-131287
  • gh-131326
  • gh-132540
  • gh-133329
  • gh-133582
  • gh-134103
  • gh-134224
  • gh-134269
  • gh-134279
  • gh-134287
  • gh-137748
  • gh-137807
  • gh-137816
  • gh-137832
  • gh-137833
  • gh-139934
  • gh-139947
  • gh-139983
  • gh-140199
  • gh-140200
  • gh-143835
  • gh-144918
  • gh-147995
  • gh-149681
  • gh-149683
  • gh-149825
  • gh-149868
  • gh-150203
  • gh-150655
  • gh-150656
  • gh-151855
  • gh-151971
  • gh-157133
  • gh-157154

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.