-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathREADME.md
More file actions
177 lines (105 loc) · 5.73 KB
/
Copy pathREADME.md
File metadata and controls
177 lines (105 loc) · 5.73 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
<p align="center">
<img src="https://github.com/mljar/variable-inspector/blob/main/media/jupyter-variable-inspector-banner.jpg?raw=true" alt="Jupyter Variable Inspector banner"/>
</p>
# Jupyter Variable Inspector
The Variable Inspector is a JupyterLab extension designed to help you manage and track variables within your notebook. It displays all your variables in one convenient location, allowing you to see their names, values, types, shapes, and sizes in real-time. This feature makes it easier to work without the need to manually print or check your variables. **It is for Python only.**
Install the extension using `pip` by following the instructions below. Variable Inspector is also included with [MLJAR Studio](https://platform.mljar.com).
## Features
### Display variables
Explore all available variables in the current notebook as a list.
<img src="https://github.com/mljar/variable-inspector/blob/main/media/jupyter-variable-inspector.gif?raw=true" alt="Jupyter Variable Inspector displays variables"/>
### Display DataFrames
You can preview the DataFrame values as an interactive table.
<img src="https://github.com/mljar/variable-inspector/blob/main/media/jupyter-variable-inspector-display-data-frame.gif?raw=true" alt="Jupyter Variable Inspector display DataFrame"/>
### Display DataFrames with updates
The preview of DataFrame will be automatically refreshed when you change it in the Python code.
<img src="https://github.com/mljar/variable-inspector/blob/main/media/jupyter-variable-inspector-update-data.gif?raw=true" alt="Jupyter Variable Inspector update data"/>
### Customize displayed columns
You can select which properties of the variables you'd like to display:

### Automatic or manual refresh
The list of variables will automatically update whenever you execute a cell. However, you can choose the Manual Refresh option to update the list at your convenience.

### Dark theme
If you prefer a darker look, a Dark Theme is also available!

## Variable Inspector in MLJAR Studio
Variable Inspector is included with MLJAR Studio, a desktop environment for Python and data analysis built on JupyterLab.
In Studio, you can keep a variable or DataFrame preview open beside a classic notebook or an AI Data Analyst conversational notebook. Open previews automatically update when your Python code changes the data.
No separate extension installation is required.
[Download MLJAR Studio](https://platform.mljar.com)
## Variable Inspector requirements
- JupyterLab >= 4.0.0
## Install extension
To install the extension, execute:
```bash
pip install variable_inspector
```
## Uninstall extension
To remove the extension, execute:
```bash
pip uninstall variable_inspector
```
## 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 variable_inspector 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 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 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 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
```
### Development uninstall
```bash
pip uninstall variable_inspector
```
In development mode, you will also need to remove the symlink created by `jupyter labextension develop`
command. To find its location, you can run `jupyter labextension list` to figure out where the `labextensions`
folder is located. Then you can remove the symlink named `variable-inspector` within that folder.
## Running end-to-end UI tests
This project uses **Playwright** to run UI tests against JupyterLab with the MLJAR extension.
### Prerequisites
- Node.js / Yarn
- Playwright installed (`jlpm playwright install`)
### How to Run Tests
You need **two terminals**:
#### 1. Start JupyterLab
In the first terminal, run:
```bash
jlpm lab
```
This will start JupyterLab at `http://localhost:8899/lab`.
#### 2. Run UI Tests
In the second terminal, run:
```bash
jlpm test:ui:headed
```
This will:
* Remove any temporary `Untitled*.ipynb` files
* Launch Playwright in **headed mode** (with a visible browser)
* Run the end-to-end tests defined in `tests/e2e`
* Remove leftover `Untitled*.ipynb` files after tests finish
### Notes
* Logs are printed to the console during test execution for easier debugging.
* If you encounter navigation timeout errors, make sure JupyterLab is fully started before running the tests.
### Packaging the extension
See [RELEASE](RELEASE.md)