[issue13875] cmd: no user documentation

2012-02-03 Thread Éric Araujo
Éric Araujo added the comment: +1 to expanding the introduction. Do you have a phrasing suggestion? > MOTW links are a more global issue that was discussion on python-dev (I > forget the outcome, > but I think it was "no"). IIRC it was on python-ideas, and (among other criticisms about licens

[issue13875] cmd: no user documentation

2012-01-26 Thread R. David Murray
R. David Murray added the comment: You can feed a cmd driven interface from stdin or via cmd.onecmd. However, I agree that the intended and primary use case is interactive. There wouldn't be much point in using cmd if the primary intent of your program wasn't interactive. -- __

[issue13875] cmd: no user documentation

2012-01-26 Thread anatoly techtonik
anatoly techtonik added the comment: What do you mean by saying it is not limited for interactive use? I thought it is used to provide command prompt for typing commands. What other use cases does it support? -- status: pending -> open ___ Python t

[issue13875] cmd: no user documentation

2012-01-26 Thread R. David Murray
R. David Murray added the comment: Well, since it isn't limited to interactive use, I don't think 'interactive' is missing. MOTW links are a more global issue that was discussion on python-dev (I forget the outcome, but I think it was "no"). I don't see anything that needs done here, but if

[issue13875] cmd: no user documentation

2012-01-26 Thread anatoly techtonik
New submission from anatoly techtonik : http://docs.python.org/library/cmd.html# Documentation for cmd module is poor to explain the value of this module to users. Intro is too abstract - phrase "simple framework for writing line-oriented command interpreters" doesn't mean much. Perhaps word