[issue32832] doctest should support custom ps1/ps2 prompts

Cheryl Sabella added the comment: Thank you for the suggestion, but per the discussion with Tim, I am closing as rejected. -- nosy: +cheryl.sabella resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32832] doctest should support custom ps1/ps2 prompts

Sergey B Kirpichev added the comment: > They support _more than one_ set of PS1/PS2 conventions. I saw this, not sure if that's required. IMHO, same effect should be possible by running doctest several times with different conventions. > Who would it help? In principle, any project, that

[issue32832] doctest should support custom ps1/ps2 prompts

Tim Peters added the comment: You missed my point about IPython: forget "In/Out arrays, etc". What you suggest is inadequate for _just_ changing PS1/PS2 for IPython. Again, read their `parse()` function. They support _more than one_ set of PS1/PS2 conventions. So the

[issue32832] doctest should support custom ps1/ps2 prompts

Sergey B Kirpichev added the comment: > are people writing an entirely different shell interface. They're rare. Or just using a different shell interface. Or even different defaults for the standard shell... And they are not rare. Almost nobody in reality use CPython

[issue32832] doctest should support custom ps1/ps2 prompts

Tim Peters added the comment: Sergey, I understand that, but I don't care. The only people I've ever seen _use_ this are people writing an entirely different shell interface. They're rare. There's no value in complicating doctest to cater to theoretical use cases that

[issue32832] doctest should support custom ps1/ps2 prompts

Sergey B Kirpichev added the comment: > doctest was intended to deal with the standard CPython terminal shell. I'd > like to keep it that way The point is: ps1/ps2 customization could be considered as part of the standard shell. If stdlib allow such changes - doctest

[issue32832] doctest should support custom ps1/ps2 prompts

Tim Peters added the comment: doctest was intended to deal with the standard CPython terminal shell. I'd like to keep it that way, but recognize that everyone wants to change everything into "a framework" ;-) How many other shells are there? As Sergey linked to, IPython

[issue32832] doctest should support custom ps1/ps2 prompts

Raymond Hettinger added the comment: Tim, what do you say, feature or feature creep, straightforward patch or can of worms? -- assignee: -> tim.peters nosy: +rhettinger, tim.peters type: -> enhancement versions: +Python 3.8

[issue32832] doctest should support custom ps1/ps2 prompts

Change by Roundup Robot : -- keywords: +patch pull_requests: +6775 stage: -> patch review ___ Python tracker ___

[issue32832] doctest should support custom ps1/ps2 prompts

New submission from Sergey B Kirpichev : The Python stdlib allows override of sys.ps1/ps2 (to make IPython-like dynamic prompts and so on). I believe it would be a good idea to support this in doctest too, to cover cases when given application uses different from defaults