Skip to content

Debug output is invisible when using pytest with pdb and pyreadline (Windows) #399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pytestbot opened this issue Dec 5, 2013 · 3 comments
Labels
type: bug problem that needs to be addressed

Comments

@pytestbot
Copy link
Contributor

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).

image depicting invisible output

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.


@pytestbot
Copy link
Contributor Author

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):


could you try disabling colorama (in py/_io/terminalwriter.py)? it is used on windows for coloring.

@pytestbot
Copy link
Contributor Author

Original comment by holger 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.

@pytestbot
Copy link
Contributor Author

Original comment by Jason 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug problem that needs to be addressed
Projects
None yet
Development

No branches or pull requests

1 participant