Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugger message bug gets printed in the IPython Console

See original GitHub issue

Problem Description

After starting an IPython Console with the standalon installer on Windows sometimes you get a message at the top regarding the debugger.

Checking seems like this was reported at https://github.com/spyder-ide/spyder/issues/16896#issuecomment-979837635 but I only notice it until now. Not totally sure if this is some sort of warning that needs to be handled/removed or something else @ccordoba12 @impact27 ?

Paste Traceback/Error Below (if applicable)


It seems the debugger cannot resolve D:\obj\windows-release\37amd64_Release\msi_python\zip_amd64\ntpath.py
This may make the debugger miss breakpoints in the standard library.
Related bug: https://bugs.python.org/issue1180193

Versions

Spyder version: 5.2.0 None
Python version: 3.7.9 64-bit
Qt version: 5.12.10
PyQt5 version: 5.12.3
Operating System: Windows 10

Issue Analytics

State:
Created 2 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

ccordoba12commented, Dec 1, 2021

Not totally sure if this is some sort of warning that needs to be handled/removed or something else @ccordoba12 @impact27 ?

This message (like the one referenced above by @impact27) is generated by pydevd, a vendored dependency of debugpy, which in turn is a dependency of IPykernel 6+. We’re not using it in our debugger, but it was introduced by the Jupyter team to implement the Debugger Adapter Protocol, which is like the LSP but for debuggers.

0reactions

dalthvizcommented, Dec 23, 2021

Hi @gaotxg a new fix was done at https://github.com/spyder-ide/spyder/pull/17050 (will be available with the next release)

Top Results From Across the Web

Why debug logs are not getting printed in console and in file

ERROR/WARNING levels are getting printed as expected. Below is the code import logging logger = logging.getLogger() fileHandler = logging.

Errors and Debugging | Python Data Science Handbook

This debugger lets the user step through the code line by line in order to see what might be causing a more difficult...

iPython console gets totally unresponsive when using large ...

This bug has made PyCharm completely useless when dealing with large datasets (not that large to be honest, just 1 million rows by...

Debugger — Spyder 5 documentation

To set this up, go to Preferences ‣ IPython Console ‣ Debugger ‣ Run code while debugging, and enter the code that you...

Issues closed in the 0.12 development cycle — IPython 7.30.0 ...

636: debugger.py: pydb broken. 808: Ctrl+C during %reset confirm message crash Qtconsole. 927: Using return outside a function crashes ipython. 919: ...