本文介绍了无法在Jupyter Notebook中创建Python 3 Notebook的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在关注本教程,当我想创建一个新的Jupyter Notebook(Python 3)时,我陷入了困境.使用以下命令创建集群:

I'm following this tutorial and I'm stuck when I want to create a new Jupyter Notebook (Python 3). The cluster is created using this command:

gcloud beta dataproc clusters create ${CLUSTER_NAME} \
 --region=${REGION} \
 --image-version=1.4 \
 --master-machine-type=n1-standard-4 \
 --worker-machine-type=n1-standard-4 \
 --bucket=${BUCKET_NAME} \
 --optional-components=ANACONDA,JUPYTER \
 --enable-component-gateway

当我访问JupyterLab并尝试创建一个新笔记本时,我可以看到:接着

When I accessing the JupyterLab and try to create a new notebook I can see:and then

控制台工作正常

提前谢谢!

推荐答案

这是支持在GCS或本地磁盘中存储笔记本的新功能的结果.

This is a consequence of the new feature to support storing notebooks either in GCS or on the local disk.

为此,将Jupyter(和JupyterLab)内部的顶级目录设置为虚拟的只读目录,该目录仅通过虚拟子目录链接到GCS和本地磁盘位置.目的是通过导航此虚拟文件层次结构来选择存储位置.

To enable that, the top-level directory inside of Jupyter (and JupyterLab) was made into a virtual, read-only directory that just links to the GCS and local disk locations via virtual subdirectories. The intention is that you choose a storage location by navigating this virtual file hierarchy.

因此,如果您尝试在顶层创建文件,则会收到错误消息,因为该顶层是只读的,但是如果您导航到其中一个子目录,则一切都会按预期进行.

So, if you try to create a file at the top-level, you will get an error because that top-level is read-only, but if you navigate into one of the subdirectories, then things will work as expected.

显然需要改善用户体验,并且该错误消息根本没有帮助,因此我们正在此处努力改善体验.

The user experience around this clearly needs to be improved, and that error message is not helpful at all, so we are working on improving the experience here.

但是,如果您选择两个存储选项之一(通过导航到子目录之一),那么事情应该会按预期进行.

However, if you choose one of the two storage options (by navigating into one of the subdirectories), then things should work as expected.

这篇关于无法在Jupyter Notebook中创建Python 3 Notebook的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-18 17:05