Metadata-Version: 2.1
Name: lckr_jupyterlab_variableinspector
Version: 3.0.3
Summary: Variable inspector extension for JupyterLab
Home-page: https://github.com/lckr/jupyterlab-variableInspector.git
Author: lckr
License: BSD-3-Clause
Description: # jupyterlab_variableinspector
        
        ![Build](https://github.com/lckr/jupyterlab-variableInspector/workflows/Build/badge.svg)
        [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/lckr/jupyterlab-variableInspector.git/master?urlpath=lab)
        
        Jupyterlab extension that shows currently used variables and their values. The goal is to provide a tool similar to the variable inspector in RStudio.
        
        This project is inspired by the [variable inspector extension for jupyter notebooks](https://github.com/ipython-contrib/jupyter_contrib_nbextensions/tree/master/src/jupyter_contrib_nbextensions/nbextensions/varInspector) and by the [inspector extension included in jupyterlab](https://github.com/jupyterlab/jupyterlab/tree/master/packages/inspector-extension).
        
        Contributions in any form are very welcome!
        
        ## Features
        
        ![Demogif](early_demo.gif)
        
        - Allows inspection of variables for both consoles and notebooks.
          - This extension is currently targets `python` as a main language but also supports the following languages with different levels of feature completeness
            - `R`  
            - `scala` via the [almond kernel](https://github.com/almond-sh/almond)
        - Allows inspection of matrices in a datagrid-viewer. This might not work for large matrices.
        - Allows an inline and interactive inspection of Jupyter Widgets.
          
        **Caveat** In order to allow variabale inspection, all content that is displayed first need to be sent from the kernel to the front end.  
        Therefore, opening large data frames with the datagrid viewer can dramatically increase your occupied memory and *significantly slow down* your browser.  
        Use at your own risk.
        
        
        ## Requirements
        
        * JupyterLab >= 3.0
        
        ### Requirements for Python functionality
        
        - `pandas` and `numpy` are required to enable matrix inspection.
        - `pyspark` for spark support.
        - `tensorflow` and `keras` to allow inspection of tf objects.
        
        ### Requirements for `ipywidgets` functionality
        
        The variable inspector can also display Jupyter interactive widgets:
        
        ![ipywidgets](./ipywidgets.png)
        
        The requirements for this functionality are:
        
        - `ipywidgets`
        - Support for widgets in JupyterLab: `jupyter labextension install @jupyter-widgets/jupyterlab-manager`
        
        ### Requirements for R functionality
        
        - The `repr` library.
          
        
        ## Install
        
        ```bash
        pip install lckr-jupyterlab-variableinspector
        ```
        
        
        ## Contributing
        
        ### Development install
        
        Note: You will need NodeJS to build the extension package.
        
        The `jlpm` command is JupyterLab's pinned version of
        [yarn](https://yarnpkg.com/) that is installed with JupyterLab. You may use
        `yarn` or `npm` in lieu of `jlpm` below.
        
        ```bash
        # Clone the repo to your local environment
        # Change directory to the lckr_jupyterlab_variableinspector directory
        # Install package in development mode
        pip install -e .
        # Link your development version of the extension with JupyterLab
        jupyter labextension develop . --overwrite
        # Rebuild extension Typescript source after making changes
        jlpm run build
        ```
        
        You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.
        
        ```bash
        # Watch the source directory in one terminal, automatically rebuilding when needed
        jlpm run watch
        # Run JupyterLab in another terminal
        jupyter lab
        ```
        
        With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).
        
        By default, the `jlpm run build` command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:
        
        ```bash
        jupyter lab build --minimize=False
        ```
        
        ### Uninstall
        
        ```bash
        pip uninstall lckr_jupyterlab_variableinspector
        ```
        
Keywords: Jupyter,JupyterLab,JupyterLab3
Platform: Linux
Platform: Mac OS X
Platform: Windows
Classifier: License :: OSI Approved :: BSD License
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Framework :: Jupyter
Requires-Python: >=3.6
Description-Content-Type: text/markdown
