Bug 499393 - Indented blocks of code make bpython unusable
Indented blocks of code make bpython unusable
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: bpython (Show other bugs)
rawhide
i586 Linux
low Severity high
: ---
: ---
Assigned To: Terje Røsten
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-06 10:06 EDT by Matteo Castellini
Modified: 2009-05-18 07:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-18 07:12:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Matteo Castellini 2009-05-06 10:06:47 EDT
Description of problem:
bpython stops interpreting code interactively when entering an indentend block of code and doesn't exit from it. AFAICT this happens only on i586 systems, while bpython works smoothly on x86_64 systems.

Version-Release number of selected component (if applicable):
bpython-0.7.1-3.fc11.noarch
python-2.6-7.fc11.i586

How reproducible: 
Always

Steps to Reproduce:
1. $ bpython
2. Run the following code:
for i in range(2):
    print i
  
Actual results:
>>> for i in range(2):
...     print i
...     
...     
... 

Expected results:
>>> for i in range(2):
...     print i
... 
0
1
>>>

Additional info:
Neither pressing Control-d nor Control-c help exiting the indented block
Comment 1 Terje Røsten 2009-05-06 16:56:32 EDT
Try to use DEL key, that works here.

>>> for i in range(2):
...     print i
...             <- Press DEL here, and then ENTER.
0
1
Comment 2 Matteo Castellini 2009-05-06 17:37:01 EDT
Yes, deleting the indented space and pressing ENTER solves the problem, but is it supposed to work this way?
Comment 3 Terje Røsten 2009-05-18 04:46:27 EDT
Unsure, I have sent a mail upstream.
Comment 4 Terje Røsten 2009-05-18 07:12:33 EDT
According to author, this is expected behaviour from bpython. I agree.

Note You need to log in before you can comment on or make changes to this bug.