<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thanks to all,<div class=""><br class=""></div><div class="">selecting python313 now worked. Actually what set the ball rolling was the fact that my jupyter is defunct.</div><div class=""><br class=""></div><div class="">It began, when jupyter under conda/anaconda3, had an outdated sympy package. It ended up in removing anaconda/conda totally from my system.</div><div class="">After that jupyter didn't work any longer:</div><div class=""><br class=""></div><span class=""><font face="Courier New" class="">$ jupyter notebook<br class="">usage: jupyter [-h] [--version] [--config-dir] [--data-dir] [--runtime-dir] [--paths] [--json] [--debug] [subcommand]<br class=""><br class="">Jupyter: Interactive Computing<br class=""><br class="">positional arguments:<br class=""> subcommand the subcommand to launch<br class=""><br class="">options:<br class=""> -h, --help show this help message and exit<br class=""> --version show the versions of core jupyter packages and exit<br class=""> --config-dir show Jupyter config dir<br class=""> --data-dir show Jupyter data dir<br class=""> --runtime-dir show Jupyter runtime dir<br class=""> --paths show all Jupyter paths. Add --json for machine-readable format.<br class=""> --json output paths as machine-readable json<br class=""> --debug output debug information about paths<br class=""><br class="">Available subcommands: 3.13 console dejavu events execute kernel kernelspec lab-3.13 labextension-3.13 labhub-3.13 migrate<br class="">nbconvert notebook-3.13 run server troubleshoot trust<br class=""><br class="">Jupyter command `jupyter-notebook` not found.<br class=""></font><br class=""><div class="">After the python313 episode the above jupyter disfunctionality persists.</div><div class=""><br class="webkit-block-placeholder"></div><div class="">An attempt to install jupyter now under python313 shows that there are 3.11 dependencies:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: "Courier New"; background-color: rgb(254, 244, 139);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">pip3 install jupyter</span></div></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: "Courier New"; background-color: rgb(254, 244, 139);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Requirement already satisfied: jupyter in /usr/local/lib/python3.11/site-packages (1.1.1)</span></div></div><div class=""><span class=""><br class=""></span></div>and lots more of references to python 3.11</span><div class=""><span class=""><br class=""></span></div><div class=""><span class=""><br class=""><blockquote type="cite" class="">Am 11.07.2025 um 11:04 schrieb Bjarne D Mathiesen via macports-users <<a href="mailto:macports-users@lists.macports.org" class="">macports-users@lists.macports.org</a>>:<br class=""><br class="">Den 11.07.2025 kl. 10.38 skrev Ryan Carsten Schmidt:<br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class="">On Jul 11, 2025, at 03:27, Bjarne D Mathiesen wrote:<br class=""><br class="">port select --set python python313<br class="">port select --set python3 python313<br class=""></blockquote><br class="">Prefix those commands with "sudo" for normal root MacPorts installations. <br class=""></blockquote><br class="">Well, I'm running under "sudo bash" under my admin account to avoid<br class="">having to prefix every admin task w/ "sudo"<br class=""><br class=""><blockquote type="cite" class=""><br class="">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. <br class=""></blockquote><br class="">We did do a concerted effort in getting rid of python27 in macports some<br class="">time back. If I remember correctly, I had a major part in updating a lot<br class="">of stuff to at least python35 at that time.<br class=""><br class="">Python27 is offically dead. It was only being kept around in a comatose<br class="">state because of a lot of stuff not having been upgraded to python3.x<br class=""><br class="">-- <br class="">Bjarne D Mathiesen<br class="">Slagelse ; Danmark ; Europa<br class="">-----------------------------------------------------------------------<br class="">denne besked er skrevet i et totalt M$-frit miljø<br class="">MacPro 2010 5.1 ; OpenCore + macOS 14.7.6 Sonoma<br class="">2 x 3,46 GHz 6-Core Intel Xeon ; 192 GB 1333 MHz DDR3 ECC RDIMM<br class="">ATI Radeon RX 590 8 GB<br class=""><br class=""></blockquote><br class=""></span></div></body></html>