Message137094
Unless the doc for a module explicitly diclaims interactive mode (as does multiproccessing), it should run interactively as documented. Batch and interactive are not mutually exclusive; python -i runs a file in batch mode and switches to interactive mode. IDLE *always* runs files this way!
Interactive exploration is a recommended way to learn Python. I agree that it would be tedious to explore the usage of argparse, for instance, by typing everything at the interactive prompt. But one could, for instance, write a file that puts fake content into sys.argv, sets up option and arg specs, and parses. After running the file in IDLE (or with python -i), one might interactively modify sys.argv or the specs and reparse to see what changes.
In any case, using a module interactively and running its test interactively are different things. If a test cannot run interactively, it should be marked as 'skip if interactive' just as with all the other skip conditions. (Skip if not self.program_name might do it.) But this is all moot for this issue. |
|
Date |
User |
Action |
Args |
2011-05-27 18:47:55 | terry.reedy | set | recipients:
+ terry.reedy, bethard, eric.araujo, michael.foord, Trundle |
2011-05-27 18:47:55 | terry.reedy | set | messageid: <1306522075.39.0.694078073313.issue11906@psf.upfronthosting.co.za> |
2011-05-27 18:47:54 | terry.reedy | link | issue11906 messages |
2011-05-27 18:47:54 | terry.reedy | create | |
|