79656279

Date: 2025-06-06 17:36:25
Score: 1.5
Natty:
Report link

The way I got past this was to blow away the venv entirely, and start fresh:

rm -rf /opt/netbox/venv
python3 -m venv venv
source /opt/netbox/venv/bin/activate
pip install -r requirements.txt
python netbox/manage.py runserver 0.0.0.0:8000 --insecure

I also made sure that the interpreter selected in VS Code was ./venv/bin/python once the new venv was created.

Still not sure why the execution context for both the debugger and the command line escaped out of the venv. That was super weird. If anyone has any idea, it would certainly help me sleep at night.

Reasons:
  • Blacklisted phrase (1): help me
  • Long answer (-0.5):
  • Has code block (-0.5):
  • Self-answer (0.5):
  • Low reputation (1):
Posted by: Colin Lacy