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
It started up the py.test and upon a fail, it it would got into pdb mode. However, The keyboard is totally non-responsive. Pressing Ctrl-C a couple times will eventually exit the pdb mode, and all the keys I had been trying to press will show up and the subsequent prompt.
Any ideas how to fix this?
My workaround was to downgrade to py.test 2.8.5, which works fine. pdb enters interactive mode and I can enter and change commands.
Happy to provide more information, but here's some version information.
(C:\Anaconda3) C:\git\glmtools>python --version
Python 3.5.2 :: Anaconda custom (64-bit)
(C:\Anaconda3) C:\Users\pquackenbush\git\glmtools>py.test --version
This is pytest version 2.9.2, imported from C:\Anaconda3\lib\site-packages\pytes
t.py
The package glmtools is something I'm working on myself. Its not a complex script. With that said, I've tried this on multiple packages (and both a Windows 7 laptop and a Windows Server 2013 virtual machine) and had the same outcome.
Thoughts?
The text was updated successfully, but these errors were encountered:
thequackdaddy
changed the title
BUG: Keyboard is non-responsive with py.test 2.9.2
BUG: Keyboard is non-responsive with py.test 2.9.2 with --pdb
Aug 20, 2016
thequackdaddy
changed the title
BUG: Keyboard is non-responsive with py.test 2.9.2 with --pdb
BUG: Keyboard is non-responsive with Windows py.test 2.9.2 with --pdb
Aug 20, 2016
Hello,
I had anaconda 4.1.1 installed on Windows. By default, that uses pytest 2.9.2. I'm working on debugging something and when I typed...
It started up the py.test and upon a fail, it it would got into
pdb
mode. However, The keyboard is totally non-responsive. Pressing Ctrl-C a couple times will eventually exit the pdb mode, and all the keys I had been trying to press will show up and the subsequent prompt.Any ideas how to fix this?
My workaround was to downgrade to py.test 2.8.5, which works fine. pdb enters interactive mode and I can enter and change commands.
Happy to provide more information, but here's some version information.
The package glmtools is something I'm working on myself. Its not a complex script. With that said, I've tried this on multiple packages (and both a Windows 7 laptop and a Windows Server 2013 virtual machine) and had the same outcome.
Thoughts?
The text was updated successfully, but these errors were encountered: