-
Notifications
You must be signed in to change notification settings - Fork 144
Replies: 1 comment · 4 replies
-
|
There are a few known issues that cause this behavior: Most are addressed in the daily builds. Would you be willing to reproduce in a daily build and let us know if it's still happening there? If so, run the Runtime Startup Diagnostics command immediately after observing the unwanted Python startup and let us know what you see (it'll tell us why Python is starting up) |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Thanks! I updated to the latest daily, and issue persists. Positron Version: 2026.04.0 build 202 I create a "New folder from template", choose R, this works: directory opens and an R console fires up. I open a directory with random .R and .Rmd files (no project files), no console boots up but instead I see "There is no session running. Use Start Session to start one." I open a Quarto project directory, and both R and Python consoles boot up, and Python becomes active. Here's the runtime startup diagnostics: |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
I looked into this a bit more. I have two very similar Quarto projects, one is a big website, other a simple manuscript, the former opens up Python and R consoles, the latter only R. I cannot see any relevant differences between projects (I created .Rproj, .Renviron, .Rprofile files in both). Mysterious. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
From those diagnostics, it looks you have an "affiliated" Python runtime for this workspace, which means that Python has gotten signaled that it belongs to that workspace. You might try running the command Interpreter: Clear Saved Interpreter from the command palette and breaking the workspace affiliation for the one you see continuing to start. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Thanks @juliasilge, while I was trying to do this I closed the Python console and accidentally restarted positron before clearing the saved interpreter. Upon reopening Python does not start up anymore. So the problem seems solved for this particular directory, although I don't know why. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, when I open a new Positron window in an empty directory (or one containing .R and .Rmd files), Positron still defaults to firing up Python. How do I make sure that Positron never opens a Python session by default, but instead starts an R session?
I added
"positron.r.interpreters.default": "/usr/local/bin/R"to my settings.json, but this only had the effect that no interpreter / session is started (even in a directory containing .R and .Rmd files). I also have"interpreters.startupBehavior": "auto", and tried "always", "recommended", and "manual", but those result in a python interpreter / session starting on startup.Positron Version: 2026.03.0 build 212
Code - OSS Version: 1.108.0
Commit: f3aae65
Date: 2026-02-26T04:57:06.999Z
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.3.0
Beta Was this translation helpful? Give feedback.
All reactions