Nope, in the jail still “command not found”.
pkg install python3 python
You can always invoke python39 or python311 to get a specific version in FreeBSD. Additionally there are “convenience packages” that you can install like above that give you the familiar commands.
The versions these finally invoke change over time as e.g. just now they switched from 3.9 to 3.11.
1 Like
Not sure i am following. If i execute “pkg version” in the jail after i performed the “pkg upgrade” last week, it now displays both versions.
py311-aioquic-1.2.0 =
py311-anyio-4.4.0 =
py311-async_generator-1.10 =
py311-attrs-24.1.0 =
py311-certifi-2024.7.4 =
py311-cffi-1.17.0 =
py311-cryptography-42.0.8_2,1 =
py311-dnspython-2.6.1,1 =
py311-h11-0.14.0 =
py311-h2-4.1.0 =
py311-hpack-4.0.0 =
py311-httpcore-1.0.5 =
py311-httpx-0.27.0_1 =
py311-hyperframe-6.0.0 =
py311-idna-3.7 =
py311-markdown-3.6 =
py311-openssl-24.1.0,1 =
py311-outcome-1.3.0_1 =
py311-packaging-24.1 =
py311-pyasn1-0.6.0 =
py311-pyasn1-modules-0.4.0 =
py311-pycparser-2.22 =
py311-pylsqpack-0.3.18 =
py311-service-identity-24.1.0 =
py311-setuptools-63.1.0_1 =
py311-sniffio-1.3.1 =
py311-socksio-1.0.0_1 =
py311-sortedcontainers-2.4.0 =
py311-trio-0.26.2 =
py39-anyio-4.3.0 ?
py39-async_generator-1.10 ?
py39-attrs-23.2.0 ?
py39-certifi-2024.2.2_1 ?
py39-cffi-1.16.0 ?
py39-cryptography-42.0.7,1 ?
py39-exceptiongroup-1.2.1 ?
py39-h11-0.14.0 ?
py39-h2-4.1.0 ?
py39-hpack-4.0.0 ?
py39-httpcore-1.0.5 ?
py39-hyperframe-6.0.0 ?
py39-idna-3.7 ?
py39-importlib-metadata-7.1.0 ?
py39-openssl-23.2.0,1 ?
py39-outcome-1.3.0_1 ?
py39-packaging-24.1 =
py39-pyasn1-0.6.0 ?
py39-pycparser-2.22 ?
py39-pylsqpack-0.3.18 ?
py39-setuptools-63.1.0_1 =
py39-sniffio-1.3.1 ?
py39-socksio-1.0.0_1 ?
py39-sortedcontainers-2.4.0 ?
py39-trio-0.25.1 ?
py39-typing-extensions-4.11.0 ?
py39-zipp-3.19.0 ?
python311-3.11.9_1 =
python39-3.9.19 =
I don’t want to remove 3.9 if i am not certain i will not be breaking stuff so how do i figure out which one is actively in use?
You need to install the python3 package to have a command named python3 available and the python package to have a command named python, respectively.
If you don’t, you can invoke both versions as python39 or python311 as necessary.
Both of the named packages (python, python3) will invoke python311 in the end, which is the default version in FreeBSD 13.3. You can keep python39 around as long as you like. Both can be in use, that’s the point of naming the packges differently instead of only having a single one with a version number.
1 Like
Honestly, it took me quite some time to figure out that you meant that python and python3 are not the actual python packages. Now i did (yes, at my age sometimes things go slow…) and executed both commands and they return this:
root@nextcloudv2:~ # python --version
Python 3.11.10
root@nextcloudv2:~ # python3 --version
Python 3.11.10
root@nextcloudv2:~ #
Does this mean that NC is using 3.11 now and i can safely remove 3.9?
No. It means whatever process calls either python, or python3, or python311 gets Python 3.11. Whatever process calls python39 gets Python 3.9.
Before that update python and python3 were referring to 3.9.
I cannot tell whatever version any other software installed in your jail might be calling.
Just remove the dang thing - you can reinstall it anytime. Python 3.9 is still a supported version …
Same here…would love to continue on a Core train BUT there is obviously no love and future in it.
I try to stay as long as I can on 13.0-U6.2 and move to scale somewhen or to leave the boat 
1 Like
Future, no. Love for it, plenty.
1 Like