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
Sticky by default not working with pytest #486
Comments
This is happening to all my team mates that use an M1 Mac like myself and I'm wondering what if PDBPP anything has to do with that. Python version is 3.8.7 by the way. |
I had the pleasure of working in an older repo this week that had a working version of pdbpp and pytest at the same time. It brought joy to an otherwise dark place. Any word on this? |
I am also having the same issue as well. It is not working with M1 mac's very nicely. |
I'm also having the same issue on an M1. |
Here, it works when I call a test this way: python -mpdb -c 'c' -m pytest --trace --pdb /path/to/my/test_module.py::my_test and have a file import pdb
class Config(pdb.DefaultConfig):
sticky_by_default = True What I'm using:
|
@jamilraichouni I revisit this every few months. Still doesn't work and I'm wondering if I'm one of the only people still caring about this. I wanted to let you know I've duplicated your exact versions and pdbrc and when I run your command I still get the same errors. |
Please try pdb++ from the master branch. |
Recently I've noticed that when placing a debugger inside a test I am not greeted with pdbpp's wonderful sticky mode which I have as an always on default in my pdbrc but instead I'm greeted with this:
Now this is not catastrophic as I am indeed inside my lovely python debugger of choice and if I were to use the next keyword the debugger would suddenly be in sticky mode but just one line later than I intended. I've localized the issue to be happening only when debugging inside pytest as my sticky by default works in any other non pytest capacity. I've tried googling this every few days but to no avail. Also of note is that I've recently switched to an m1 mac which has been full of incompatibility challenges that have been stubborn but not impossible to fix so I would not be surprised to find this to be a side effect related to apple silicon as none of my other python peers use the same cpu.
pdbpp==0.10.3
pytest==7.1.2
The text was updated successfully, but these errors were encountered: