You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vdom currently has some incompatibilities with JupyterLab that are forcing us to remove it from the core distribution. Given that vdom has not been maintained for 3+ years, we think that the best way of doing so would be to first migrate the vdom Jupyter extension packages underneath the nteract org umbrella. That way, if vdom ever gets revived again, the vdom extension packages can also be easily revived. Without this migration, users who wish to fork/contribute would be forced to dig through the old JupyterLab git history to extract the extension source code.
A few questions:
Are there any objections to this proposed migration?
Can we get consensus on a repository name? I was thinking nteract/vdom-extension.
The text was updated successfully, but these errors were encountered:
vdom
currently has some incompatibilities with JupyterLab that are forcing us to remove it from the core distribution. Given thatvdom
has not been maintained for 3+ years, we think that the best way of doing so would be to first migrate thevdom
Jupyter extension packages underneath thenteract
org umbrella. That way, ifvdom
ever gets revived again, thevdom
extension packages can also be easily revived. Without this migration, users who wish to fork/contribute would be forced to dig through the old JupyterLab git history to extract the extension source code.A few questions:
nteract/vdom-extension
.The text was updated successfully, but these errors were encountered: