166b7753-21ce-4dc8-bf77-8f2b0cc9e0b5
commented
23 years ago A long array, such as from Numeric Python is displayed as \<array 3434 343421 4324234 .... 324234 34234>, with part of the array replaced with elipses.
Often, this is enough information, but unfortunately not always. IDLE cannot tell you how many items the array had (even approximately), and it is impossible to see the complete output or repr(). This is a bug, as a stack viewer ought to let you see what is on the stack.
I'd suggest that long reprs() that get truncated this way ought to be viewable in their entirety, perhaps by clicking on them.
A fancier option would be to have IDLE look for a getitem() attribute, and allow anything that has getitem() (or perhaps getitem() and len()) to be displayed in the same format that build-in python arrays are displayed in.
gvanrossum
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields: ```python assignee = 'https://github.com/gvanrossum' closed_at =
created_at =
labels = ['expert-IDLE', 'type-feature']
title = "IDLE doesn't display long arrays well"
updated_at =
user = 'https://bugs.python.org/gpk'
```
bugs.python.org fields:
```python
activity =
actor = 'gvanrossum'
assignee = 'gvanrossum'
closed = True
closed_date = None
closer = None
components = ['IDLE']
creation =
creator = 'gpk'
dependencies = []
files = []
hgrepos = []
issue_num = 217686
keywords = []
message_count = 2.0
messages = ['2164', '2165']
nosy_count = 2.0
nosy_names = ['gvanrossum', 'gpk']
pr_nums = []
priority = 'low'
resolution = 'later'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue217686'
versions = []
```