https://bugs.kde.org/show_bug.cgi?id=426866
--- Comment #6 from Gaël de Chalendar (aka Kleag) <kle...@gmail.com> --- In fact, running and debugging both work with the correct setting. After setting the full path to my virtual env python interpreter in the "Configure project" dialog, I tried to run and debug while keeping just "python" as the "Script interpreter" in the "Launch configurations" dialog. And it failed like described above. After setting the full path to my virtual env python interpreter also in the "Script interpreter" in the "Launch configurations" dialog, it now works (running and debugging). My two conclusions/wishes: - when setting a full path to the python interpreter in the launch configuration, it should become the default one in the launch configs - there should be detection the start of kdevelop starting from a venv and a explicit message to the user stating that it should start from the system one -- You are receiving this mail because: You are watching all bug changes.
