Failure of remote connection

I am getting a failure message when connecting from a Macintosh to a remote Linux server that says.

Unsupported: Python 0.0.1 (System) failed to start.
Error
The Python sqlite3 extension is required but not installed for interpreter: Python. Missing the system library for SQLite?

I don't understand from where Positron is getting a python 0.0.1, and I don't understand what is meant by 'Python sqlite3 extension' nor where to get one nor whether that is on the remote or local machine.

This is what I am working with.

On the local Mac, Mac OS 14.8.4 (Sonoma), I have the default system python,

$ which sqlite3
/usr/bin/sqlite3

$ sqlite3
SQLite version 3.43.2 2023-10-10 13:08:14
Enter ".help" for usage hints.

$ python3
Python 3.9.6 (default, Nov 11 2024, 03:15:38) 
[Clang 16.0.0 (clang-1600.0.26.6)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> sqlite3.version_info
(2, 6, 0)

On the remote machine,

$ rpm -qa | grep sqlite
sqlite-libs-3.34.1-7.el9_3.x86_64
sqlite-3.34.1-7.el9_3.x86_64

$ sqlite3
SQLite version 3.34.1 2021-01-20 14:10:07
Enter ".help" for usage hints.

$ python3
Python 3.9.21 (main, Feb 10 2025, 00:00:00) 
[GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> sqlite3.version_info
(2, 6, 0)

$ uname -r
5.14.0-570.72.1.el9_6.x86_64
$ cat /etc/redhat-release 
Red Hat Enterprise Linux release 9.6 (Plow)

Sorry to be fumbling so much with this! :frowning:

-- bennet

Thank you for giving Positron a try! Can you share what version you are using when you observe these problems?

We have logged Python: PET detects Homebrew python with version "0.0.1" · Issue #10424 · posit-dev/positron · GitHub, although it's not something we've always been able to reproduce. It can't be exactly that, because of course that report seems specific to Homebrew.

We previously fixed a problem on Windows that looked a bit similar, in Python starts up "Unsupported: Python 0.0.1" interpreter · Issue #9186 · posit-dev/positron · GitHub, but again, in the end we found that to be a Windows-specific problem.

Some of those problems have been related to using the "native" Python locator vs. one that is written in Javascript. What happens if you change the python.locator setting to "js"?
https://positron.posit.co/python-installations.html#locator-type

Have you tried installing a non-system Python on the remote server for use with your data science work? That would generally be considered best practice anyway, and to make a venv so that you don't mess around with the system Python. My current preferred tool for this is uv:

This is the version I installed.

Positron Version: 2026.02.1 build 5
Code - OSS Version: 1.106.0
Commit: 693b6d13ba5d61566bec7f5a4a46126eff7bbbe1
Date: 2026-02-10T19:05:16.756Z (2 wks ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 23.6.0

Ah, it was detecting a homebrew installation on the Mac that I had forgot about. I removed that, then it asked about install pip and iPykernel using a /bin/python that doesn't seem to exist on my Mac.

As I am only exploring this for someone else, I think I'll have them try themself, since it seems that per-user customization may be needed (or needs to be undone) on both sides. If they run into problems, they'll be able to modify their environment accordingly.