> On Oct 4, 2021, at 10:57 PM, Christopher Jones <[email protected]> > wrote: > > > >> On 4 Oct 2021, at 9:18 pm, Artemio González López via macports-users >> <[email protected] >> <mailto:[email protected]>> wrote: >> >>> >> >> Ciao Giuseppe, >> >> I am happy to report that after following your advice everything worked as >> advertised. I only experienced a very minor glitch, namely that for some >> reason (probably a minor bug?) the >> /opt/local/Library/Frameworks/Versions/3.9/bin directory where jupyter >> resides is not in the $PATH, so you must add it by hand if you want to >> invoke (say) jupyter with just its name. > > No, that is not a bug but intentional. it is that way because in principle > you could have multiple versions installed, for different python versions. > For that reason one specific python version cannot place its binaries under > the default ${prefix}/bin with the nominal names, as that would prevent > others from then being installed. > > The port does in fact install binaries, but they are suffixed with the python > version > > Oberon ~/Projects/MacPorts/ports > port contents py39-jupyter_client | grep > bin > > /opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/jupyter-kernel > > /opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/jupyter-kernelspec > /opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/jupyter-run > /opt/local/bin/jupyter-kernel-3.9 > /opt/local/bin/jupyter-kernelspec-3.9 > /opt/local/bin/jupyter-run-3.9 > > > so to run a specific version (for a given python version) run XYZ-3.9 etc. > > Chris > > >> >> Thanks a lot for your patience and help! >> >> Artemio
Hi, Chris, Thanks a lot for your excellent answer! Now everything is clear to me. Artemio Artemio Gonzalez Lopez [email protected]
smime.p7s
Description: S/MIME cryptographic signature
