On 2025-07-11 at 11:05:55 UTC-0400 (Fri, 11 Jul 2025 17:05:55 +0200)
Christoph Kukulies via macports-users <[email protected]>
is rumored to have said:
Thanks to all,
selecting python313 now worked. Actually what set the ball rolling was
the fact that my jupyter is defunct.
It began, when jupyter under conda/anaconda3, had an outdated sympy
package. It ended up in removing anaconda/conda totally from my
system.
After that jupyter didn't work any longer:
$ jupyter notebook
usage: jupyter [-h] [--version] [--config-dir] [--data-dir]
[--runtime-dir] [--paths] [--json] [--debug] [subcommand]
Jupyter: Interactive Computing
positional arguments:
subcommand the subcommand to launch
options:
-h, --help show this help message and exit
--version show the versions of core jupyter packages and exit
--config-dir show Jupyter config dir
--data-dir show Jupyter data dir
--runtime-dir show Jupyter runtime dir
--paths show all Jupyter paths. Add --json for
machine-readable format.
--json output paths as machine-readable json
--debug output debug information about paths
Available subcommands: 3.13 console dejavu events execute kernel
kernelspec lab-3.13 labextension-3.13 labhub-3.13 migrate
nbconvert notebook-3.13 run server troubleshoot trust
Jupyter command `jupyter-notebook` not found.
After the python313 episode the above jupyter disfunctionality
persists.
An attempt to install jupyter now under python313 shows that there are
3.11 dependencies:
pip3 install jupyter
Requirement already satisfied: jupyter in
/usr/local/lib/python3.11/site-packages (1.1.1)
and lots more of references to python 3.11
That sounds like the pip3 you are running is pip311. You need to use
'port select' to pick the right one:
sudo port select pip3 pip313
You may get better results by sticking to MacPorts entirely or Python
tools (e.g. pip) entirely for installation. I.e. install the
py313-jupyter port
It is also possible that some of the dependencies of a complex tool like
Jupyter are not yet updated to use Python 3.13.
Am 11.07.2025 um 11:04 schrieb Bjarne D Mathiesen via macports-users
<[email protected]>:
Den 11.07.2025 kl. 10.38 skrev Ryan Carsten Schmidt:
On Jul 11, 2025, at 03:27, Bjarne D Mathiesen wrote:
port select --set python python313
port select --set python3 python313
Prefix those commands with "sudo" for normal root MacPorts
installations.
Well, I'm running under "sudo bash" under my admin account to avoid
having to prefix every admin task w/ "sudo"
I believe I read somewhere that the python community recommends that
"python" always be python 2.x, never python 3.x. Programs that want
to use python 3.x should use the program name "python3". If "port
select python" currently allows versions of python 3.x to be
selected, we may want to change that.
We did do a concerted effort in getting rid of python27 in macports
some
time back. If I remember correctly, I had a major part in updating a
lot
of stuff to at least python35 at that time.
Python27 is offically dead. It was only being kept around in a
comatose
state because of a lot of stuff not having been upgraded to python3.x
--
Bjarne D Mathiesen
Slagelse ; Danmark ; Europa
-----------------------------------------------------------------------
denne besked er skrevet i et totalt M$-frit miljø
MacPro 2010 5.1 ; OpenCore + macOS 14.7.6 Sonoma
2 x 3,46 GHz 6-Core Intel Xeon ; 192 GB 1333 MHz DDR3 ECC RDIMM
ATI Radeon RX 590 8 GB
--
Bill Cole
[email protected] or [email protected]
(AKA @[email protected] and many *@billmail.scconsult.com
addresses)
Not Currently Available For Hire
