- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Issue37768
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2019-08-05 20:56 by taleinat, last changed 2022-04-11 14:59 by admin.
| Pull Requests | |||
|---|---|---|---|
| URL | Status | Linked | Edit |
| PR 15140 | open | taleinat, 2019-08-05 21:03 | |
| PR 26561 | closed | taleinat, 2021-06-06 15:28 | |
| Messages (5) | |||
|---|---|---|---|
| msg349073 - (view) | Author: Tal Einat (taleinat) * ![]() |
Date: 2019-08-05 20:56 | |
Currently, IDLE just writes the entire help message into the shell. If auto-squeezing is enabled, then long help messages are automatically squeezed, following which the help text can be viewed in a text viewer or expanded inline. This is still not great UX. I propose to simply have help(object) open a text viewer with the help text. There's actually an old (2007) comment in Lib\idlelib\pyshell.py by KBK that this should be done. See related discussion in issue #35855. |
|||
| msg349075 - (view) | Author: Tal Einat (taleinat) * ![]() |
Date: 2019-08-05 21:04 | |
See PR GH-15140. |
|||
| msg349076 - (view) | Author: Tal Einat (taleinat) * ![]() |
Date: 2019-08-05 21:06 | |
Raymond, I'm interested in your opinion on this. |
|||
| msg351059 - (view) | Author: Terry J. Reedy (terry.reedy) * ![]() |
Date: 2019-09-03 05:13 | |
For myself, I only want this for 'large' outputs. I prefer something like the following left alone.
>>> help('continue')
The "continue" statement
************************
continue_stmt ::= "continue"
"continue" may only occur syntactically nested in a "for" or "while"
loop, but not nested in a function or class definition within that
loop. It continues with the next cycle of the nearest enclosing loop.
When "continue" passes control out of a "try" statement with a
"finally" clause, that "finally" clause is executed before really
starting the next loop cycle.
Related help topics: while, for
The threshhold for squeezer should be good enough. I think of this as autosqueeze + autoexpand if this if the first output after '>>>' and the statement began with 'help('. An advantage of doing it this way is that the squeezer button remains after dismissing the viewer.
Also, I suspect that most people who disable squeezer would not like this either.
|
|||
| msg351065 - (view) | Author: Terry J. Reedy (terry.reedy) * ![]() |
Date: 2019-09-03 05:42 | |
I should have said, 'who disable autosqueeze'. Anyway, an option to disable help autoview will make me more comfortable adding it. A similar change would be to add 'Squeeze & View' to the context menu. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:18 | admin | set | github: 81949 |
| 2021-06-06 15:28:24 | taleinat | set | pull_requests: + pull_request25150 |
| 2019-09-03 05:42:42 | terry.reedy | set | messages: + msg351065 |
| 2019-09-03 05:13:44 | terry.reedy | set | messages: + msg351059 |
| 2019-08-05 21:06:54 | taleinat | set | nosy:
+ rhettinger messages: + msg349076 |
| 2019-08-05 21:04:26 | taleinat | set | messages: + msg349075 |
| 2019-08-05 21:03:51 | taleinat | set | keywords:
+ patch stage: needs patch -> patch review pull_requests: + pull_request14878 |
| 2019-08-05 20:56:06 | taleinat | create | |


