Open layne-sadler opened 3 years ago
We will first upgrade the source-only extension, as this should be straightforward with any luck, and we will look into the prebuilt extension thereafter, yes.
Is the effort to get jupyter-dash extension prebuild for jupyterlab-3 still ongoing ? or has it been drop for a "no interest" or "no time" reason ?
also, I've got a fail trying to get it work on PyPy3-3.7.5 / Jupyterlab-3.1.0rc1, but not sure who is responsible, if someone can tell me
I'm trying Dash with PyPy3 because I suppose it removes the "c-interface" speed debt for PyPy3.
Hi guys. Can the maintainers provide an update on this issue, please? It is the only extension we use which requires us to rebuild jupyterlab. Not a huge deal, but a pre-built extension will be a nice-to-have.
Migration guide for jupyterlab extensions going from jupyterlab v2 to v3: https://jupyterlab.readthedocs.io/en/stable/extension/extension_migration.html#jupyterlab-2-x-to-3-x
Any chance a prebuilt version will be released?
Any update?
This entire package is obsolete, its functionality has been integrated into the main Dash package. If anyone is interested in helping modernize JupyterDash packaging the Dash repo is the place to continue this discussion.
As described in the Jupyter 3.0 blog post:
Are there plans to prebuild the "jupyterlab-dash JupyterLab extension?"
In my experience, it requires a lot of troubleshooting. This could help reduce friction.