I am using:
- Python: 3.11.0
- Django: 4.2.8
- djangorestframework 3.14.0
- sqlite: 3.38.5
When I'm debugging and I use 'n' to go over a method, I sometimes get a segfault where there is no problem running the code normally. I can move my 'ipdb.set_trace()' to immediately after the call that caused the segfault, rerun the test and continue debugging but this is tedious.
One cause I've tracked, is under the django reverse function. Here, the <URLResolver <module 'rest_framework.urls' from '/home/paul/wk/cliosoft/sosmgrweb/venv/lib/python3.11/site-packages/rest_framework/urls.py'> (rest_framework:rest_framework) 'api-auth/'> causes the segfault when its _populate method is invoked.
I could start upgrading everything but this is a large application with many dependencies and I'd like to be confident that this problem will be eliminated if I go down that road.
Does anyone know what the cause of this is and how I can resolve it?
Python 3.11.0 was causing this problem. Upgrading the venv to use python 3.11.8 has got rid of it and I can now use ipdb without it segfaulting (as tested so far).