-
Notifications
You must be signed in to change notification settings - Fork 139
Closed
Labels
area: kernelsIssues related to Jupyter kernels and LSP serversIssues related to Jupyter kernels and LSP serversbugSomething isn't workingSomething isn't workinglang: pythonperformance
Milestone
Description
Positron Version:
main as of 5/31
Steps to reproduce the issue:
- Load a pandas data frame in a fresh interpreter, such as
import numpy as np
import pandas as pd
df = pd.DataFrame(
{"a": [1, 2, 3, np.NaN, 5],
"b": [" foo", " bar", "baz", "qux", "potato"],
"c": [True, False, True, False, True],
"d": [True, None, None, False, True],
'e': pd.date_range('2000-01-01', periods=5),
'f': ['foo', True, None, False, True]
}
)
- restart the interpreter
Here's an example timeline
2024-05-31 14:27:12.004 [info] Python (3.11.8) language client state changed running => stopped
2024-05-31 14:27:46.106 [info] Creating Positron Python 3.11.8 language client (port 50077)
2024-05-31 14:27:46.107 [info] Python (3.11.8) language client state changed stopped => starting
2024-05-31 14:27:46.159 [info] Python (3.11.8) language client init successful
2024-05-31 14:27:46.159 [info] Python (3.11.8) language client state changed starting => running
What did you expect to happen?
For the interpreter to restart within 5 seconds
Were there any error messages in the output or Developer Tools console?
some, but unsure if related
Metadata
Metadata
Assignees
Labels
area: kernelsIssues related to Jupyter kernels and LSP serversIssues related to Jupyter kernels and LSP serversbugSomething isn't workingSomething isn't workinglang: pythonperformance
