Marc Wouts
1 min readAug 24, 2018

--

Thanks Chadwick for trying. We don’t have exactly the same configuration, but I would expect it not to matter much. Tonight I tried it on my windows desktop, it worked with the logs

C:\Users\Marco\AppData\Local\conda\conda\envs\python3\python.exe "C:\Program Files\JetBrains\PyCharm Community Edition 2018.1.4\helpers\pydev\pydevd_attach_to_process\attach_pydevd.py" --port 52572 --pid 1976
Attaching to a process with PID=1976
Connected to pydev debugger (build 181.5087.37)
Attach finished successfully.

I’m not sure how you could solve that, maybe a checklist would be

  1. make sure jupyter notebook server is started outside of PyCharm. You’re not going to attach to that process, but to the kernel used by your notebook.
  2. does the Jupyter messaging works? Can you connect to Jupyter kernel with jupyter console, using in a terminal:
jupyter console --existing kernel-d1b9a862-1f04-403b-82fb-5b820c0a0f89.json 

3. Does attach work? Can you try it with another process started outside of PyCharm? I see that there might be a special setting for Ubuntu, see https://www.jetbrains.com/help/pycharm/attaching-to-local-process.html

Hope that will help — please let us know.

--

--

Marc Wouts
Marc Wouts

Written by Marc Wouts

Author of Jupytext and ITables. I love maths, data visualization and programming in mixed languages

Responses (1)