Does not work with Jupyter Lab 3

[dpriedel]

Hi
This is a very useful extension but it doesn't work with the new version 3.0 of JupyterLab

The extension installs OK but when you right click in a cell to open the variable inspector an empty tab results. There are column headings but no variables are displayed.
Also, clicking the close box on the tab does not work.

[FuriouslyCurious]

Seconded. When I open VariableInspector in JupyterLab 3.0, I do not even get column headings - just a blank tab.

The extension is enabled and listed in the extensions tab as active.

[okkymabruri]

Yeah, we are in the same problem. I will wait for the next upgrade

[nmweizi]

Yeah, we are in the same problem. I will wait for the next upgrade

[nmweizi]

I have same problem

[popcsev]

I also have the same issue with Jupyterlab 3.0.1 installed. Moreover, after clicking on the close button the variable inspector becomes blank and it does not close.

[jdtuck]

Same issues observed here

[M00NSH0T]

I also ran into this... should have checked here before trying, because now I'm unable to successfully get this working after rolling back to Jupyterlab 2.

Have any of you tried installing this on a fresh install / environment?

I've always had issues getting this extension working after changing versions of Jupyterlab within a Conda environment. Uninstall / reinstall doesn't usually prompt you to rebuild even if you shut down the server after each step. Manual rebuild doesn't always bring back the 'Open Variable Inspector' option, and even when it does, it's just blank and won't let you move it to another pane, like what I'm seeing now in Jupyterlab 3. Last time this happened (when I upgraded from jupyterlab 1 to 2) I spent hours tracking / deleting files within my anaconda environment related to this extension after uninstall /reinstall failed to get it working. In the end, I just wiped my whole conda environment and created a new one, which let me use this invaluable extension once more. I haven't gone that far yet, but might be worth a shot.

[pfren1998]

I also encounter the same issue with Jupyterlab 3.0.3^^

[xsola]

I also encountered the same problem, is there any solution?

[LucaPalmer]

I'm having the same problem as well. I really got used to having this thing around so I'd love to see it get fixed.

[lckr]

Hey guys, I'm currently working on the migration to JLab 3.0, should be available later today.

[dpriedel]

Great....Thanks!!!!

[lckr]

The migration to 3.0 should be done now.
Note: From now on the extension will be distributed via pip, this might also prevent problems such as described here:

I've always had issues getting this extension working after changing versions of Jupyterlab within a Conda environment. Uninstall / reinstall doesn't usually prompt you to rebuild even if you shut down the server after each step. [...]

If you run into any problems regarding the migration, please reopen.

[M00NSH0T]

ok I just tried installing this with pip and I hit an error. I've only ever used the extension manager within jupyter, however, so IDK if this is specific to this update or not. Also, I should point out, I'm doing this on my windows machine first... haven't tried on Linux yet, but wouldn't be surprised if perhaps this is windows specific.

Here's the tail end of the output.... it was quite long. I can add the rest if it would help, but I think this captures where the issue was.

  error: could not create 'build\bdist.win-amd64\wheel\lckr_jupyterlab_variableinspector-3.0.1.data\data\share\jupyter\labextensions\@lckr\jupyterlab_variableinspector': The system cannot find the path specified
  ----------------------------------------
  ERROR: Failed building wheel for lckr-jupyterlab-variableinspector
Failed to build lckr-jupyterlab-variableinspector
ERROR: Could not build wheels for lckr-jupyterlab-variableinspector which use PEP 517 and cannot be installed directly```

[M00NSH0T]

also, this was v3.0.1 and I see you've just released 3.0.2 in the past few minutes. pip doesn't recognize that new version yet... I'll try again shortly to see if that fixes the problem.

[dpriedel]

Installed on Linux and works fine. Thanks Dave R.

…

On 1/15/21 11:27 AM, lckr wrote: The migration to 3.0 should be done now. *Note:* From now on the extension will be distributed via pip If you run into any problems regarding the migration, please reopen. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#172 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUOHSXVHMSWTKB6NZU7Z43S2BUF5ANCNFSM4VJ64JLQ>.

[M00NSH0T]

ok this appears to be a windows issue per this thread. Downgrading pip with pip install pip==18.1 got it to install, but while it appears to work at first glance with me being able to open the variable inspector and move to other panes, the problem is that once I start creating variables in my notebooks, it remains blank. I did a rebuild of jupyter lab and restarted it, but still, nothing seems to show.

Just to confirm - this extension did / does work on JupyterLab2 in Windows when I installed via the extension manager. Not sure if it would be possible to make this available that way again in JupyterLab3?

[rvillalba-novetta]

Will the new version be available in conda?

[lckr]

@M00NSH0T , I pushed some fixes that might solve your problem. Please try the new v3.0.3 release and let me know if that works for you.

@rvillalba-novetta Good suggestion. I will look into it.

[dana-and-monsters]

Hi @lckr! Thanks for a great extension! I updated jupyter lab to 3.0.7 thinking that this would still work fine with this extension but the extension stopped working. I tried re-installing with pip and now I am getting the error "ERROR: Could not build wheels for lckr-jupyterlab-variableinspector which use PEP 517 and cannot be installed directly". Thank you so much for all of your help with this!

[M00NSH0T]

@dana-and-monsters did you try downgrading pip to 18.1?

[will-tha-mise]

Hi, I had the same issue as @dana-and-monsters - tried downgrading pip and got:

  Collecting pywin32>=1.0; sys_platform == "win32" (from jupyter-core->jupyterlab==3.*,>=3.0.0rc13)
    Could not find a version that satisfies the requirement pywin32>=1.0; sys_platform == "win32" (from jupyter-core->jupyterlab==3.*,>=3.0.0rc13) (from versions: )

  No matching distribution found for pywin32>=1.0; sys_platform == "win32" (from jupyter-core->jupyterlab==3.*,>=3.0.0rc13)
  You are using pip version 18.1, however version 21.0.1 is available.
  You should consider upgrading via the 'python -m pip install --upgrade pip' command.

[miGa77]

For me the same issue as @dana-and-monsters and @wbolton .
Spent the whole day to get this working, but haven't found a solution.

error: could not create 'build\bdist.win-amd64\wheel\lckr_jupyterlab_variableinspector-3.0.6.data\data\share\jupyter\labextensions\@lckr\jupyterlab_variableinspector': Das System kann den angegebenen Pfad nicht finden

Before I had same error messages like
ERROR: Could not build wheels for lckr-jupyterlab-variableinspector which use PEP 517 and cannot be installed directly and Could not find a version that satisfies the requirement pywin32>=1.0; sys_platform == "win32" (from jupyter-core->jupyterlab==3.*,>=3.0.0rc13) (from versions: ) .

[lckr]

You can now also obtain/install the extension from npm again, this could circumvent these path issues that happen on windows.
Please refer to the installation instructions in the readme.

[sravya267]

Still no luck for me. On jupyter 3.0. Tried both pip and npm.

[Lilac-in-April]

still not working. I got this:

note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for lckr-jupyterlab-variableinspector
Failed to build lckr-jupyterlab-variableinspector
ERROR: Could not build wheels for lckr-jupyterlab-variableinspector, which is required to install pyproject.toml-based projects