You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using PyCharm on Windows 10 and remote debug into a Linux VM. So in this case there are mapped paths between where the Python scripts are locally and where they are located remotely (IOW, Windows style paths locally and Unix style paths remotely), e.g:
When an exception is thrown, you will see something in the console like this:
Traceback (most recent call last):
File "/home/user/projects/foo/bar.py", line 123, in MyFunction
In the original output console, the "/home/user/projects/foo/bar.py" path will be a link, and clicking on it will take you to the corresponding source file, even though the file is located on Windows and the real path is "C:\projects\foo\bar.py".
However in the Grep Console, the source file will not be shown as a link, so one cannot click on it to go to the line where the exception occurred.
Interestingly, if I explicitly print a source line but use the Windows path style, it shows up as a link in Grep Console, e.g.:
print(' File "C:\\projects\\foo\\bar.py", line 123, in MyFunction')
The above is shown as a link in the Grep Console output and is clickable.
[edit] Note the file must actually exist locally for it to be shown as a link.
So it seems Grep Console only treats Windows style paths on Windows as links, while PyCharm treats both Windows and Unix style paths as links.
I'm not sure who is responsible for displaying a source file as a link in Grep Console. If it is the Grep Console plugin itself then maybe if it simply displays anything within quotes after "File" that looks like either a Windows or a Unix file path as a link to the file, PyCharm will probably do the mapping to the local Windows file automatically when it is clicked, not sure.
PyCharm 2019.1.1 (Professional Edition)
Build #PY-191.6605.12, built on April 3, 2019
JRE: 11.0.2+9-b159.34 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
The text was updated successfully, but these errors were encountered:
Hi,
I'm using PyCharm on Windows 10 and remote debug into a Linux VM. So in this case there are mapped paths between where the Python scripts are locally and where they are located remotely (IOW, Windows style paths locally and Unix style paths remotely), e.g:
Path Mapping:
C:\projects\foo -> /home/user/projects/foo
When an exception is thrown, you will see something in the console like this:
In the original output console, the "/home/user/projects/foo/bar.py" path will be a link, and clicking on it will take you to the corresponding source file, even though the file is located on Windows and the real path is "C:\projects\foo\bar.py".
However in the Grep Console, the source file will not be shown as a link, so one cannot click on it to go to the line where the exception occurred.
Interestingly, if I explicitly print a source line but use the Windows path style, it shows up as a link in Grep Console, e.g.:
The above is shown as a link in the Grep Console output and is clickable.
[edit] Note the file must actually exist locally for it to be shown as a link.
So it seems Grep Console only treats Windows style paths on Windows as links, while PyCharm treats both Windows and Unix style paths as links.
I'm not sure who is responsible for displaying a source file as a link in Grep Console. If it is the Grep Console plugin itself then maybe if it simply displays anything within quotes after "File" that looks like either a Windows or a Unix file path as a link to the file, PyCharm will probably do the mapping to the local Windows file automatically when it is clicked, not sure.
PyCharm 2019.1.1 (Professional Edition)
Build #PY-191.6605.12, built on April 3, 2019
JRE: 11.0.2+9-b159.34 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
The text was updated successfully, but these errors were encountered: