-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix erroneous instructions to setup a devel environment #64
Comments
Ran into pretty much the same issue when following the instruction. After the first two steps (cloning the repo and moving into
The same command seems to be working in the main repository directory, but when trying to follow it up with the next step
and the log of the error is as follows:
There is a possibility that I've done something wrong or omitted some steps in my env / jupyter setup, but seeing that other people had encountered the same issue it might not be the case. I am working on I would be really grateful for any clarification/help in that regard. Thanks |
@Y3drk since you are on Windows, does enabling symbolic links help by any chance?
|
@krassowski I've read about it but haven't tried it. I don't have much time to spare so I can't promise it, but if I ever go back to it I'll try it |
I was able to get a development environment setup by modifying the instructions a bit. Before I would get to the
That was fixed by adding an extra Here were my steps: Install node version 20, python 3.11. And then execute the following commands in the RISE repo:
|
Fixes #64 Co-authored-by: Frédéric Collonval <fcollonval@users.noreply.github.com>
followed the Contributing section of README.md but ran into the following error
so I see several improvements that can be done there
reword
into
because there is a subfolder named
jupyterlab_rise
so it's confusing, esp. as the toplevel repo may not be called thateither add a dependency so that jupyter-labextension gets installed by
pip install -e .
or instruct developers topip install jupyter
like I did (maybe there's a better way to do that ?)actually provide a
package.json
if that's what it takes ?The text was updated successfully, but these errors were encountered: