Issue with Python syntax highlighting not working with 2025.02.0-171

[sudarshan227]

Positron and OS details:

Positron Version: 2025.02.0 (system setup) build 171
Code - OSS Version: 1.96.0
Commit: 55f7331
Date: 2025-02-10T16:01:00.400Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100

Interpreter details:

Python 3.11.8

Describe the issue:

I am having an issue with python syntax highlighting not showing up (meaning all characters in a script, whether a .py, .ipynb, or .qmd file). What is interesting is that this only appears as an issue in the latest version of positron (2025.02.0-171). I can uninstall this version and go back to 2025.02.0-137 and the syntax highlighting works again as desired. I then reinstall 2025.02.0-171 and python syntax highlighting goes back to not working. Hence, I am wondering if there is a fix that can get the python syntax highlighting to start working again for 2025.02.0-171?

[jonvanausdeln]

@sudarshan227 thank you for your report. I am seeing some highlighting for a simple python file on my system. Could you please share an example of what you were seeing before and also how it looks now?

[apcamargo]

I'm having the same issue here. Positron doesn't show syntax highlighting for any Python file. I'm using 2025.03.0 connected to a remote server.

[apcamargo]

It looks like the issue extends beyond syntax highlighting. Some other features are also not working properly. For example, the editor is not closing quotation marks automatically.

[jberkh]

I am also having this issue, but only when working via the remote SSH functionality. When opening a python file on W11 it works as expected.

[sudarshan227]

I can confirm that I am seeing this using Remote SSH feature into WSL2, only parentheses are colored as blue.

…

On Fri, Feb 28, 2025 at 6:40 AM Jari Berkhout ***@***.***> wrote: I am also having this issue, but only when working via the remote SSH functionality. When opening a python file on W11 it works as expected. — Reply to this email directly, view it on GitHub <#6420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGVYKO5RMBMJKREMOAMTBU32SBDKFAVCNFSM6AAAAABXSJTLKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJQGQZDSMRSG4> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: jberkh]*jberkh* left a comment (posit-dev/positron#6420) <#6420 (comment)> I am also having this issue, but only when working via the remote SSH functionality. When opening a python file on W11 it works as expected. — Reply to this email directly, view it on GitHub <#6420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGVYKO5RMBMJKREMOAMTBU32SBDKFAVCNFSM6AAAAABXSJTLKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJQGQZDSMRSG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[apcamargo]

A list of the features I noticed are not working:

• Syntax highlighting
• Auto-close quotes
• When selecting a text and pressing single/double quote (or parenthesis), the text gets replaced instead of put within the quotes.
• Shortcut to comment one or more lines is not working.

[juliasilge]

Thank you all! We can reproduce this problem with the Python LSP in remote SSH sessions.