<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="">I finally got everything tidied up, running Python 3.11 now. My `jupyter notebook` invoking problem (jupyter-notebook not found) got solved when I came to the conclusion that<div class="">selecting jupyter to the right py311-jupyter and doing so for py-sympy.</div><div class=""><br class=""></div><div class="">Thanks again to all.</div><div class=""><br class=""></div><div class="">--</div><div class="">Christoph</div><div class=""><br class=""><div class=""><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">Am 12.07.2025 um 11:26 schrieb Christoph Kukulies via macports-users <<a href="mailto:macports-users@lists.macports.org" class="">macports-users@lists.macports.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="content-isolator__container"><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thanks. Then I'm wondering why /opt/local/bin/jupyter*<div class="">is not being used.</div><div class=""><br class=""></div><span class=""><font face="Courier New" class="">$ ls /opt/local/bin/ju*<br class="">/opt/local/bin/jupyter-3.13<br class="">/opt/local/bin/jupyter-console-3.13<br class="">/opt/local/bin/jupyter-dejavu-3.13<br class="">/opt/local/bin/jupyter-events-3.13<br class="">/opt/local/bin/jupyter-execute-3.13<br class="">/opt/local/bin/jupyter-kernel-3.13<br class="">/opt/local/bin/jupyter-kernelspec-3.13<br class="">/opt/local/bin/jupyter-lab-3.13<br class="">/opt/local/bin/jupyter-labextension-3.13<br class="">/opt/local/bin/jupyter-labhub-3.13<br class="">/opt/local/bin/jupyter-migrate-3.13<br class="">/opt/local/bin/jupyter-nbconvert-3.13<br class="">/opt/local/bin/jupyter-notebook-3.13<br class="">/opt/local/bin/jupyter-run-3.13<br class="">/opt/local/bin/jupyter-server-3.13<br class="">/opt/local/bin/jupyter-troubleshoot-3.13<br class="">/opt/local/bin/jupyter-trust-3.13<br class=""></font><br class="">All my troubles would have been blown away ( command jupyter-notebook not found) if the correct mechanism</span><div class=""><span class="">would point to these programs.</span></div><div class=""><span class=""><br class=""></span></div><div class=""><span class="">If I run </span></div><div class=""><span class=""><br class=""></span></div><div class=""><font face="Courier New" class="">$ jupyter 3.13 notebook</font></div><div class=""><br class=""></div><div class="">everything works, but this would be a crock.</div><div class=""><br class=""></div><div class=""><span class=""><br class=""></span></div><div class=""><span class="">--</span></div><div class=""><span class="">Christoph</span></div><div class=""><span class=""><br class=""><blockquote type="cite" class="">Am 12.07.2025 um 10:24 schrieb Ryan Carsten Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>>:<br class=""><br class="">On Jul 12, 2025, at 02:56, Christoph Kukulies wrote:<br class=""><blockquote type="cite" class=""><br class=""></blockquote><blockquote type="cite" class="">I tried that:<br class=""><br class=""> sudo port install py313-jupyter<br class=""><br class="">But /usr/local/bin/jupyter still points at python3.11<br class=""><br class=""><br class="">#!/usr/local/opt/python@3.11/bin/python3.11<br class=""># -*- coding: utf-8 -*-<br class="">import re<br class="">import sys<br class="">from jupyter_core.command import main<br class="">if __name__ == '__main__':<br class=""> sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])<br class=""> sys.exit(main())<br class=""><br class="">Where does /usr/local/bin/jupyter actually stem from?<br class=""></blockquote><br class="">MacPorts uses /opt/local by default. <br class=""><br class="">/usr/local is for software you install manually. On Intel Macs, Homebrew takes over this location. Attempting to configure MacPorts to use this location will produce a loud warning explaining that we don't recommend using that location. <br class=""><br class="">Having Homebrew and MacPorts installed on the same computer will cause problems and is not recommended. Neither is installing software to /usr/local manually. <br class=""><br class="">See <a href="https://trac.macports.org/wiki/FAQ#usrlocal" class="">https://trac.macports.org/wiki/FAQ#usrlocal</a><br class=""></blockquote><br class=""></span></div></div></div></div></blockquote></div><br class=""></div></body></html>