-
Notifications
You must be signed in to change notification settings - Fork 8
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
Installation process for development #8
Comments
Jupyter-packaging was outdated; nowadays, Jupyter uses Hatch. https://github.com/jupyter/jupyter-packaging UPD: |
There is also another section, [tool.jupyter-releaser.hooks], which seems important if you want to perform a release. The question is, why do we also need to release to Jupyter, instead of just making it possible to install from PyPI? What are the benefits of adding it there as well?" |
When an extension is being used, the method Therefore, you need to include some code like this in your import json
from pathlib import Path
__version__ = "0.1.0"
HERE = Path(__file__).parent.resolve()
with (HERE / "labextension" / "package.json").open() as fid:
data = json.load(fid)
def _jupyter_labextension_paths():
return [{
"src": "labextension",
"dest": data["name"]
}] Here is the for package in package_candidates:
try:
m = importlib.import_module(package)
if hasattr(m, "_jupyter_labextension_paths"):
return m, m._jupyter_labextension_paths()
except Exception as exc:
errors.append(exc)
msg = f"There is no labextension in {module}. Errors encountered: {errors}"
raise ModuleNotFoundError(msg) Note have not found any docs about it .... |
Problem
Hello!
I found that installing
echo_kernel
for development isn't straightforward. I followed the steps described in the contributions section but still encountered some issues. I'll try to summarize them and share the steps I followed. Perhaps then we can update the README, as it seems the current instructions might be outdated.Suggested Improvement
The text was updated successfully, but these errors were encountered: