-
-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usage of %pip leads to an error in 4.1.0-1 and newer bundled environment #784
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
@KTBL-KristofferSchneider I was able to reproduce it on Windows, I will be investigating the root cause. In the mean time you can use the terminal to install the packages you need. Please see the instructions here. |
I have further tested, which release started to contain this problem. As far as I have tested it, it seems to start with Version v4.1.0-1. Furthermore, it seems like there are more problems, than a non-working For example: until 4.1.0-1 I used to install perspective using Example-Code from datetime import date, datetime
import numpy as np
import pandas as pd
import perspective
from perspective import PerspectiveWidget, Table
data = pd.DataFrame({
"int": np.arange(100),
"float": [i * 1.5 for i in range(100)],
"bool": [True for i in range(100)],
"date": [date.today() for i in range(100)],
"datetime": [datetime.now() for i in range(100)],
"string": [str("A" * i) for i in range(100)]
})
table = perspective.Table(data, index="float")
PerspectiveWidget(data) Once the messagebox has shown the message, that the kernel will be restarted, the following messages appear within the notebook-log:
Important is to always use the bundled environment. I don't know if the problem using |
Description
When using the latest release of jupyterlab-desktop (v4.1.2-1) and creating a new environment based on the bundled environment,
%pip
will no longer be usable in a code-cell within a notebook. I haven't tested, if this bug persists in older releases as well yet. But the problem was tested (and confirmend) on three different windows 10 devices.Reproduce
%pip --version
I have set the jupyterlab-desktop logs to debug-level, but could not find any related log messages. Also, the Notebook-execution log (view > show log console) did not show any causes.
Expected behavior
Expected is the correct execution of
pip
and that the output of the command is displayed in a result cell.Context
Troubleshoot Output
If further information is required, just let me know and I'll try to provide it.
The text was updated successfully, but these errors were encountered: