Author Topic: Messages when debugging Python  (Read 260 times)


  • Community Member
  • Posts: 33
  • Hero Points: 2
Messages when debugging Python
« on: February 15, 2023, 12:36:19 pm »
I get the following messages that seem to be caused by python code that is supplied by SE. What is the explanation here?

Code: [Select]
C:\Users\ebbe\projects\myproject\test>C:\Python311\python.exe -u -Xfrozen_modules=off  "C:\Program Files\SlickEdit Pro 27.0.1\resource/tools/ptvsd" --host --port 5678 --wait "C:\Program Files\SlickEdit Pro 27.0.1\resource/tools/ptvsd/" C:\Users\ebbe\projects\myproject\test\test_config\ ConfigLoad
C:\Program Files\SlickEdit Pro 27.0.1\resource\tools\ptvsd\_vendored\pydevd\ DeprecationWarning: currentThread() is deprecated, use current_thread() instead
  curr_thread_id = get_current_thread_id(threadingCurrentThread())
C:\Program Files\SlickEdit Pro 27.0.1\resource\tools\ptvsd\_vendored\pydevd\ DeprecationWarning: isDaemon() is deprecated, get the daemon attribute instead
  if not t.isDaemon() or hasattr(t, "__pydevd_main_thread"):

SE running on Windows 10, fully updated including hotfix 2.

And in case someone is wondering about this option:
Code: [Select]
-Xfrozen_modules=off It  turns off a bunch of warnings about not being able to find frozen files. It is a workaround for a bug in pydev and it was suggested by than Guido van Rossum (no less).


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1794
  • Hero Points: 151
Re: Messages when debugging Python
« Reply #1 on: February 15, 2023, 02:03:38 pm »
The Pydev debugging backend was put in a couple of years ago.  This is the first time I've seen a report on these deprecations, and looking at the versions of Python I have on my dev systems, I'm going to guess these came into effect for Python >= 3.10. 

I'll take a closer look at it later.  I'm not up to date on what's happened with the pydevd backend since Microsoft decided to switch away from it to what appeared to be a renamed fork.  So I might be able to pull updates that address the warnings, or I might just need to patch it myself.

Thanks for the report.