You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally reported by: Jason R. Coombs (BitBucket: jaraco, GitHub: jaraco)
I recently installed pyreadline (as part of iPython) into my Python 3.3 64-bit environment on Windows 8.1.
With pyreadline 2.0 installed, py.test 2.4.2 displays invisible text when using PDB (either through pytest.set_trace or using the --pdb option).
If I uninstall pyreadline, the problem goes away.
This issue is probably as much an issue with pyreadline as pytest. I can't dig further at the moment, but I wanted to capture the issue here. I appreciate any suggestions or efforts to identify or fix the issue, but I don't expect it. I'll plan to investigate deeper in the future as time permits.
Original comment byholger krekel (BitBucket: hpk42, GitHub: hpk42):
I tried to reproduce on my Windows box on Python3.3. I installed pytest trunk (from mercurial checkout) and pyreadline and invoked "py.test x.py" with x.py containing a test that imports pdb and pdb.set_trace(). Worked fine. So i am marking this issue invalid for now. Feel free to re-open that with the precise steps that produce the bad behaviour.
Original comment byJason R. Coombs (BitBucket: jaraco, GitHub: jaraco):
You're right. I'm not experiencing the problem in a simple test, so I need to do more work to trace the cause. Thanks for looking into this and for the terminalwriter suggestion.
Originally reported by: Jason R. Coombs (BitBucket: jaraco, GitHub: jaraco)
I recently installed pyreadline (as part of iPython) into my Python 3.3 64-bit environment on Windows 8.1.
With pyreadline 2.0 installed, py.test 2.4.2 displays invisible text when using PDB (either through pytest.set_trace or using the --pdb option).
If I uninstall pyreadline, the problem goes away.
This issue is probably as much an issue with pyreadline as pytest. I can't dig further at the moment, but I wanted to capture the issue here. I appreciate any suggestions or efforts to identify or fix the issue, but I don't expect it. I'll plan to investigate deeper in the future as time permits.
The text was updated successfully, but these errors were encountered: