Closed castal closed 1 year ago
I think this is the same as issue #28. Please try:
rm -rf ~/Library/Application\ Support/SageMath/Jupyter
I have tested on Ventura, and SageMath can launch a Jupyter notebook with no trouble. Probably you had a Jupyter server running when you started the upgrade and it was rudely killed.
Bingo!!! Thanks very much!
On Sun, Mar 26, 2023 at 8:06 PM Marc Culler @.***> wrote:
I think this is the same as issue #28 https://github.com/3-manifolds/Sage_macOS/issues/28. Please try: rm -rf ~/Library/Application\ Support/SageMath/Jupyter
— Reply to this email directly, view it on GitHub https://github.com/3-manifolds/Sage_macOS/issues/53#issuecomment-1484319964, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJG25IL7GN7SU26R6N4OITW6DRZLANCNFSM6AAAAAAWIPMVYY . You are receiving this because you authored the thread.Message ID: @.***>
Glad to hear it.
I recently upgraded to macOS Ventura, and that seems to have broken the ability of Sage_macOS to access the Jupyter notebook. It was working just fine under macOS 12 (Monterey), but now the Chrome browser is telling me:
When I ask for more details, I get:
But I am not using an antivirus application and my mac tells me that the macOS Firewall is inactive.
I am OK for now just using a little shell script, "sage -n jupyter --notebook-dir [my sage directory]", but I thought that if you haven't upgraded to Ventura, then maybe you won't have seen this hiccup.