Skip to content
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

installing ipykernel looks successful after hitting permission denied #10478

Closed
Tracked by #11092
Yoyokrazy opened this issue Jun 16, 2022 · 1 comment · Fixed by #11107
Closed
Tracked by #11092

installing ipykernel looks successful after hitting permission denied #10478

Yoyokrazy opened this issue Jun 16, 2022 · 1 comment · Fixed by #11107
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug notebook-getting-started

Comments

@Yoyokrazy
Copy link
Contributor

Issue Type: Bug

ran cell with fresh interpreter in path, prompted to install ipykernel.

Installed ipykernel via dialogue, looked successful

error message upon next run of cell that ipykernel was not present, command given in error message to force-reinstall didn't fix problem either.

Extension version: 2022.6.1001691033
VS Code version: Code - Insiders 1.69.0-insider (6f7c824a826ff0ccaf4de05d6fe0aac3be7bc136, 2022-06-16T05:16:21.134Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info
Item Value
CPUs Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.59GB (17.98GB free)
Process Argv --crash-reporter-id 62122f1b-5534-43ca-aa21-fca29c482163
Screen Reader no
VM 0%
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
vsc_aa:30263845
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30404738
wslgetstarted:30449409
vscscmwlcmt:30465136
cppdebug:30492333
pylanb8912:30496796
vsclangdf:30492506

Logs Info Visual Studio Code - Insiders (1.69.0-insider, undefined, desktop) Jupyter Extension Version: 2022.6.100. Python Extension Version: 2022.9.11661004. Workspace folder c:\Users\t-mlively\Documents\dev_testing info 13:48:11.495: ZMQ install verified. User belongs to experiment group 'jupyterTest' User belongs to experiment group 'jupyterEnhancedDataViewer' info 13:48:15.53: LSP Notebooks experiment is enabled info 13:48:17.419: Experiment status for python is {"enabled":true,"optInto":[],"optOutFrom":[]} info 13:48:17.688: Active Interpreter in Python API for resource '' is c:\Python310\python.exe, EnvType: Global, EnvName: '', Version: 3.10.5 info 13:48:17.882: Active Interpreter in Python API for resource 'Untitled-1.ipynb' is c:\Python310\python.exe, EnvType: Global, EnvName: '', Version: 3.10.5 info 13:48:18.808: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher' (Python Path: , EnvType: Global, EnvName: '', Version: 3.10.5) for 'Untitled-1.ipynb' (disableUI=true) info 13:48:18.810: Creating raw notebook for resource 'Untitled-1.ipynb' info 13:48:18.810: Computing working directory for resource 'Untitled-1.ipynb' info 13:48:18.812: Starting raw kernel 'Python 3.10.5 64-bit' for interpreter c:\Python310\python.exe info 13:48:18.977: Preferred Remote kernel for Untitled-1.ipynb is undefined info 13:48:18.978: Find preferred kernel for Untitled-1.ipynb with metadata {"orig_nbformat":4,"language_info":{"name":"python"}} & preferred interpreter c:\Python310\python.exe info 13:48:18.980: Preferred Remote kernel for Untitled-1.ipynb is undefined info 13:48:18.981: Preferred kernel .jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher is exact match info 13:48:18.984: PreferredConnection: .jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher found for NotebookDocument: Untitled-1.ipynb info 13:48:19.34: Kernel launching with ports 9000,9001,9002,9003,9004. Start port is 9000 info 13:48:19.795: Widget Message: Received IPyWidgetMessages.IPyWidgets_IsReadyRequest info 13:48:20.903: Process Execution: > c:\Python310\python.exe -m pip list > c:\Python310\python.exe -m pip list info 13:48:21.153: Process Execution: > c:\Python310\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)" > c:\Python310\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)" warn 13:48:22.730: Stderr output when getting ipykernel version & path Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'ipykernel' for c:\Python310\python.exe info 13:48:22.737: Creating daemon process for c:\Python310\python.exe with env variables count 64 info 13:48:22.744: Process Execution: > c:\Python310\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 11928 > c:\Python310\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 11928 info 13:48:23.62: get interrupthandle daemon info 13:48:23.559: Process Execution: > c:\Python310\python.exe -m ipykernel_launcher --ip=127.0.0.1 --stdin=9003 --control=9001 --hb=9000 --Session.signature_scheme="hmac-sha256" --Session.key=b"9860b6f3-dc24-43d3-80ea-8e0868a0c0a9" --shell=9002 --transport="tcp" --iopub=9004 --f=c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928u00xYe6tO4YI.json > c:\Python310\python.exe -m ipykernel_launcher --ip=127.0.0.1 --stdin=9003 --control=9001 --hb=9000 --Session.signature_scheme="hmac-sha256" --Session.key=b"9860b6f3-dc24-43d3-80ea-8e0868a0c0a9" --shell=9002 --transport="tcp" --iopub=9004 --f=c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928u00xYe6tO4YI.json info 13:48:23.560: Process Execution: cwd: ~\Documents\dev_testing cwd: ~\Documents\dev_testing warn 13:48:23.670: StdErr from Kernel Process c:\Python310\python.exe: No module named ipykernel_launcher

error 13:48:23.673: Disposing kernel process due to an error [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
error 13:48:23.675: c:\Python310\python.exe: No module named ipykernel_launcher

info 13:48:23.675: kill daemon
error 13:48:23.680: Failed to connect raw kernel session: Error: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
warn 13:48:23.688: Error occurred while trying to start the kernel, options.disableUI=true [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
warn 13:48:23.690: Failed to delete connection file c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928u00xYe6tO4YI.json [Error: ENOENT: no such file or directory, unlink 'c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928u00xYe6tO4YI.json'] {
errno: -4058,
code: 'ENOENT',
syscall: 'unlink',
path: 'c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928u00xYe6tO4YI.json'
}
info 13:48:23.713: Preferred Remote kernel for Untitled-1.ipynb is undefined
info 13:48:23.713: Find preferred kernel for Untitled-1.ipynb with metadata {"orig_nbformat":4,"language_info":{"name":"python"}} & preferred interpreter c:\Python310\python.exe
info 13:48:23.715: Preferred Remote kernel for Untitled-1.ipynb is undefined
info 13:48:23.716: Preferred kernel .jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher is exact match
info 13:48:23.719: Preferred Remote kernel for Untitled-1.ipynb is undefined
error 13:48:27.372: Live Notebook not available for Untitled-1.ipynb
error 13:48:31.717: Live Notebook not available for Untitled-1.ipynb
info 13:48:34.852: Execute Cell 0 Untitled-1.ipynb
info 13:48:34.860: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher' (Python Path: , EnvType: Global, EnvName: '', Version: 3.10.5) for 'Untitled-1.ipynb' (disableUI=false)
info 13:48:34.865: Creating raw notebook for resource 'Untitled-1.ipynb'
info 13:48:34.871: Computing working directory for resource 'Untitled-1.ipynb'
info 13:48:34.876: Starting raw kernel 'Python 3.10.5 64-bit' for interpreter c:\Python310\python.exe
info 13:48:35.91: Kernel launching with ports 9008,9009,9010,9011,9012. Start port is 9000
info 13:48:35.110: Process Execution: > c:\Python310\python.exe -c "import ipykernel; print(ipykernel.version); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.file)"

c:\Python310\python.exe -c "import ipykernel; print(ipykernel.version); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.file)"
info 13:48:35.146: Creating daemon process for c:\Python310\python.exe with env variables count 64
info 13:48:35.153: Process Execution: > c:\Python310\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 11928
c:\Python310\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 11928
warn 13:48:35.184: Stderr output when getting ipykernel version & path Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'ipykernel' for c:\Python310\python.exe
info 13:48:35.355: get interrupthandle daemon
info 13:48:35.363: Process Execution: > c:\Python310\python.exe -m ipykernel_launcher --ip=127.0.0.1 --stdin=9011 --control=9009 --hb=9008 --Session.signature_scheme="hmac-sha256" --Session.key=b"16f8b584-3382-4acf-8439-c5adf703990a" --shell=9010 --transport="tcp" --iopub=9012 --f=c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928WCffnQDfrKjq.json
c:\Python310\python.exe -m ipykernel_launcher --ip=127.0.0.1 --stdin=9011 --control=9009 --hb=9008 --Session.signature_scheme="hmac-sha256" --Session.key=b"16f8b584-3382-4acf-8439-c5adf703990a" --shell=9010 --transport="tcp" --iopub=9012 --f=c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928WCffnQDfrKjq.json
info 13:48:35.364: Process Execution: cwd: ~\Documents\dev_testing
cwd: ~\Documents\dev_testing
warn 13:48:35.441: StdErr from Kernel Process c:\Python310\python.exe: No module named ipykernel_launcher

error 13:48:35.446: Disposing kernel process due to an error [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
error 13:48:35.448: c:\Python310\python.exe: No module named ipykernel_launcher

info 13:48:35.448: kill daemon
error 13:48:35.453: Failed to connect raw kernel session: Error: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
warn 13:48:35.460: Error occurred while trying to start the kernel, options.disableUI=false [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
warn 13:48:35.462: Kernel Error, context = start [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
warn 13:48:35.467: Failed to delete connection file c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928WCffnQDfrKjq.json [Error: ENOENT: no such file or directory, unlink 'c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928WCffnQDfrKjq.json'] {
errno: -4058,
code: 'ENOENT',
syscall: 'unlink',
path: 'c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928WCffnQDfrKjq.json'
}
info 13:48:35.479: Process Execution: > c:\Python310\python.exe -c "import ipykernel"

c:\Python310\python.exe -c "import ipykernel"
info 13:48:35.581: installMissingDependencies c:\Python310\python.exe, ui.disabled=false for resource 'Untitled-1.ipynb'
info 13:48:35.601: Process Execution: > c:\Python310\python.exe -c "import ipykernel"
c:\Python310\python.exe -c "import ipykernel"
info 13:48:35.732: Process Execution: > c:\Python310\python.exe -c "import pip"
c:\Python310\python.exe -c "import pip"
info 13:48:39.739: Process Execution: > c:\Python310\python.exe -c "import pip"
c:\Python310\python.exe -c "import pip"
info 13:48:39.918: Process Execution: > c:\Python310\python.exe -m pip install -U ipykernel
c:\Python310\python.exe -m pip install -U ipykernel
info 13:48:40.934: Collecting ipykernel

info 13:48:40.938: Using cached ipykernel-6.15.0-py3-none-any.whl (133 kB)

info 13:48:40.974: Requirement already satisfied: packaging in c:\python310\lib\site-packages (from ipykernel) (21.3)

info 13:48:40.976: Requirement already satisfied: psutil in c:\python310\lib\site-packages (from ipykernel) (5.9.1)

info 13:48:40.977: Requirement already satisfied: traitlets>=5.1.0 in c:\python310\lib\site-packages (from ipykernel) (5.3.0)
Requirement already satisfied: pyzmq>=17 in c:\python310\lib\site-packages (from ipykernel) (23.1.0)

info 13:48:40.979: Requirement already satisfied: nest-asyncio in c:\python310\lib\site-packages (from ipykernel) (1.5.5)

info 13:48:40.980: Requirement already satisfied: tornado>=6.1 in c:\python310\lib\site-packages (from ipykernel) (6.1)

info 13:48:41.83: Collecting ipython>=7.23.1

info 13:48:41.87: Using cached ipython-8.4.0-py3-none-any.whl (750 kB)

info 13:48:41.117: Requirement already satisfied: jupyter-client>=6.1.12 in c:\python310\lib\site-packages (from ipykernel) (7.3.4)

info 13:48:41.119: Requirement already satisfied: matplotlib-inline>=0.1 in c:\python310\lib\site-packages (from ipykernel) (0.1.3)

info 13:48:41.121: Requirement already satisfied: debugpy>=1.0 in c:\python310\lib\site-packages (from ipykernel) (1.6.0)

info 13:48:41.197: Requirement already satisfied: decorator in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (5.1.1)
Requirement already satisfied: jedi>=0.16 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.18.1)

info 13:48:41.201: Requirement already satisfied: colorama in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.4.5)

info 13:48:41.204: Requirement already satisfied: setuptools>=18.5 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (58.1.0)

info 13:48:41.207: Requirement already satisfied: pickleshare in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.7.5)
Requirement already satisfied: backcall in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.2.0)

info 13:48:41.211: Requirement already satisfied: pygments>=2.4.0 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (2.12.0)

info 13:48:41.213: Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (3.0.29)
Requirement already satisfied: stack-data in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.3.0)

info 13:48:41.246: Requirement already satisfied: entrypoints in c:\python310\lib\site-packages (from jupyter-client>=6.1.12->ipykernel) (0.4)

info 13:48:41.248: Requirement already satisfied: python-dateutil>=2.8.2 in c:\python310\lib\site-packages (from jupyter-client>=6.1.12->ipykernel) (2.8.2)

info 13:48:41.250: Requirement already satisfied: jupyter-core>=4.9.2 in c:\python310\lib\site-packages (from jupyter-client>=6.1.12->ipykernel) (4.10.0)

info 13:48:41.264: Requirement already satisfied: pyparsing!=3.0.5,>=2.0.2 in c:\python310\lib\site-packages (from packaging->ipykernel) (3.0.9)

info 13:48:41.281: Requirement already satisfied: parso<0.9.0,>=0.8.0 in c:\python310\lib\site-packages (from jedi>=0.16->ipython>=7.23.1->ipykernel) (0.8.3)

info 13:48:41.295: Requirement already satisfied: pywin32>=1.0 in c:\python310\lib\site-packages (from jupyter-core>=4.9.2->jupyter-client>=6.1.12->ipykernel) (304)

info 13:48:41.309: Requirement already satisfied: wcwidth in c:\python310\lib\site-packages (from prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0->ipython>=7.23.1->ipykernel) (0.2.5)

info 13:48:41.330: Requirement already satisfied: six>=1.5 in c:\python310\lib\site-packages (from python-dateutil>=2.8.2->jupyter-client>=6.1.12->ipykernel) (1.16.0)

info 13:48:41.351: Requirement already satisfied: executing in c:\python310\lib\site-packages (from stack-data->ipython>=7.23.1->ipykernel) (0.8.3)

info 13:48:41.352: Requirement already satisfied: asttokens in c:\python310\lib\site-packages (from stack-data->ipython>=7.23.1->ipykernel) (2.0.5)
Requirement already satisfied: pure-eval in c:\python310\lib\site-packages (from stack-data->ipython>=7.23.1->ipykernel) (0.2.2)

info 13:48:41.466: Installing collected packages: ipython, ipykernel

info 13:48:41.780: ERROR: Could not install packages due to an OSError: [WinError 5] Access is denied: 'c:\Python310\share'
Consider using the --user option or check the permissions.

info 13:48:41.787: WARNING: You are using pip version 22.0.4; however, version 22.1.2 is available.
You should consider upgrading via the 'c:\Python310\python.exe -m pip install --upgrade pip' command.

error 13:48:42.159: Failed to install ipykernel WARNING: You are using pip version 22.0.4; however, version 22.1.2 is available.
You should consider upgrading via the 'c:\Python310\python.exe -m pip install --upgrade pip' command.

info 13:48:42.163: Dispose Kernel 'Untitled-1.ipynb' associated with 'Untitled-1.ipynb'
error 13:48:42.168: Error in execution [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
error 13:48:42.170: Error in execution (get message for cell) [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
info 13:48:42.195: Process Execution: > c:\Python310\python.exe -c "import ipykernel"

c:\Python310\python.exe -c "import ipykernel"
info 13:53:28.82: Execute Cell 0 Untitled-1.ipynb
info 13:53:28.89: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher' (Python Path: , EnvType: Global, EnvName: '', Version: 3.10.5) for 'Untitled-1.ipynb' (disableUI=false)
info 13:53:28.95: Creating raw notebook for resource 'Untitled-1.ipynb'
info 13:53:28.102: Computing working directory for resource 'Untitled-1.ipynb'
info 13:53:28.110: Starting raw kernel 'Python 3.10.5 64-bit' for interpreter c:\Python310\python.exe
info 13:53:28.279: Kernel launching with ports 9016,9017,9018,9019,9020. Start port is 9000
info 13:53:28.297: Process Execution: > c:\Python310\python.exe -c "import ipykernel; print(ipykernel.version); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.file)"
c:\Python310\python.exe -c "import ipykernel; print(ipykernel.version); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.file)"
info 13:53:28.342: Creating daemon process for c:\Python310\python.exe with env variables count 64
info 13:53:28.349: Process Execution: > c:\Python310\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 11928
c:\Python310\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 11928
warn 13:53:28.437: Stderr output when getting ipykernel version & path Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'ipykernel' for c:\Python310\python.exe
info 13:53:28.601: get interrupthandle daemon
info 13:53:28.607: Process Execution: > c:\Python310\python.exe -m ipykernel_launcher --ip=127.0.0.1 --stdin=9019 --control=9017 --hb=9016 --Session.signature_scheme="hmac-sha256" --Session.key=b"be81bff1-9fab-4ac8-b994-48def79d58e8" --shell=9018 --transport="tcp" --iopub=9020 --f=c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928TXWKDkhItOyw.json
c:\Python310\python.exe -m ipykernel_launcher --ip=127.0.0.1 --stdin=9019 --control=9017 --hb=9016 --Session.signature_scheme="hmac-sha256" --Session.key=b"be81bff1-9fab-4ac8-b994-48def79d58e8" --shell=9018 --transport="tcp" --iopub=9020 --f=c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928TXWKDkhItOyw.json
info 13:53:28.608: Process Execution: cwd: ~\Documents\dev_testing
cwd: ~\Documents\dev_testing
warn 13:53:28.677: StdErr from Kernel Process c:\Python310\python.exe: No module named ipykernel_launcher

error 13:53:28.684: Disposing kernel process due to an error [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
error 13:53:28.686: c:\Python310\python.exe: No module named ipykernel_launcher

info 13:53:28.687: kill daemon
error 13:53:28.693: Failed to connect raw kernel session: Error: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
warn 13:53:28.706: Error occurred while trying to start the kernel, options.disableUI=false [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
warn 13:53:28.708: Kernel Error, context = start [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
warn 13:53:28.716: Failed to delete connection file c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928TXWKDkhItOyw.json [Error: ENOENT: no such file or directory, unlink 'c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928TXWKDkhItOyw.json'] {
errno: -4058,
code: 'ENOENT',
syscall: 'unlink',
path: 'c:\Users\t-mlively\AppData\Roaming\jupyter\runtime\kernel-v2-11928TXWKDkhItOyw.json'
}
info 13:53:28.734: Process Execution: > c:\Python310\python.exe -c "import ipykernel"

c:\Python310\python.exe -c "import ipykernel"
info 13:53:28.925: installMissingDependencies c:\Python310\python.exe, ui.disabled=false for resource 'Untitled-1.ipynb'
info 13:53:28.942: Process Execution: > c:\Python310\python.exe -c "import ipykernel"
c:\Python310\python.exe -c "import ipykernel"
info 13:53:29.67: Process Execution: > c:\Python310\python.exe -c "import pip"
c:\Python310\python.exe -c "import pip"
info 13:53:40.417: Process Execution: > c:\Python310\python.exe -c "import pip"
c:\Python310\python.exe -c "import pip"
info 13:53:40.440: Process Execution: > c:\Python310\python.exe -m pip list
c:\Python310\python.exe -m pip list
info 13:53:40.548: Process Execution: > c:\Python310\python.exe -m pip install -U ipykernel
c:\Python310\python.exe -m pip install -U ipykernel
info 13:53:41.583: Collecting ipykernel

info 13:53:41.604: Using cached ipykernel-6.15.0-py3-none-any.whl (133 kB)

info 13:53:41.674: Requirement already satisfied: psutil in c:\python310\lib\site-packages (from ipykernel) (5.9.1)

info 13:53:41.681: Requirement already satisfied: traitlets>=5.1.0 in c:\python310\lib\site-packages (from ipykernel) (5.3.0)

info 13:53:41.683: Requirement already satisfied: ipython>=7.23.1 in c:\python310\lib\site-packages (from ipykernel) (8.4.0)

info 13:53:41.684: Requirement already satisfied: nest-asyncio in c:\python310\lib\site-packages (from ipykernel) (1.5.5)

info 13:53:41.688: Requirement already satisfied: jupyter-client>=6.1.12 in c:\python310\lib\site-packages (from ipykernel) (7.3.4)

info 13:53:41.691: Requirement already satisfied: packaging in c:\python310\lib\site-packages (from ipykernel) (21.3)

info 13:53:41.695: Requirement already satisfied: pyzmq>=17 in c:\python310\lib\site-packages (from ipykernel) (23.1.0)

info 13:53:41.698: Requirement already satisfied: matplotlib-inline>=0.1 in c:\python310\lib\site-packages (from ipykernel) (0.1.3)

info 13:53:41.699: Requirement already satisfied: tornado>=6.1 in c:\python310\lib\site-packages (from ipykernel) (6.1)

info 13:53:41.701: Requirement already satisfied: debugpy>=1.0 in c:\python310\lib\site-packages (from ipykernel) (1.6.0)

info 13:53:41.748: Requirement already satisfied: backcall in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.2.0)

info 13:53:41.749: Requirement already satisfied: pygments>=2.4.0 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (2.12.0)

info 13:53:41.750: Requirement already satisfied: jedi>=0.16 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.18.1)

info 13:53:41.752: Requirement already satisfied: colorama in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.4.5)

info 13:53:41.754: Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (3.0.29)

info 13:53:41.756: Requirement already satisfied: decorator in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (5.1.1)

info 13:53:41.758: Requirement already satisfied: setuptools>=18.5 in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (58.1.0)

info 13:53:41.759: Requirement already satisfied: pickleshare in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.7.5)
Requirement already satisfied: stack-data in c:\python310\lib\site-packages (from ipython>=7.23.1->ipykernel) (0.3.0)

info 13:53:41.776: Requirement already satisfied: jupyter-core>=4.9.2 in c:\python310\lib\site-packages (from jupyter-client>=6.1.12->ipykernel) (4.10.0)

info 13:53:41.778: Requirement already satisfied: python-dateutil>=2.8.2 in c:\python310\lib\site-packages (from jupyter-client>=6.1.12->ipykernel) (2.8.2)

info 13:53:41.779: Requirement already satisfied: entrypoints in c:\python310\lib\site-packages (from jupyter-client>=6.1.12->ipykernel) (0.4)

info 13:53:41.793: Requirement already satisfied: pyparsing!=3.0.5,>=2.0.2 in c:\python310\lib\site-packages (from packaging->ipykernel) (3.0.9)

info 13:53:41.811: Requirement already satisfied: parso<0.9.0,>=0.8.0 in c:\python310\lib\site-packages (from jedi>=0.16->ipython>=7.23.1->ipykernel) (0.8.3)

info 13:53:41.819: Requirement already satisfied: pywin32>=1.0 in c:\python310\lib\site-packages (from jupyter-core>=4.9.2->jupyter-client>=6.1.12->ipykernel) (304)

info 13:53:41.823: Requirement already satisfied: wcwidth in c:\python310\lib\site-packages (from prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0->ipython>=7.23.1->ipykernel) (0.2.5)

info 13:53:41.833: Requirement already satisfied: six>=1.5 in c:\python310\lib\site-packages (from python-dateutil>=2.8.2->jupyter-client>=6.1.12->ipykernel) (1.16.0)

info 13:53:41.850: Requirement already satisfied: executing in c:\python310\lib\site-packages (from stack-data->ipython>=7.23.1->ipykernel) (0.8.3)

info 13:53:41.852: Requirement already satisfied: asttokens in c:\python310\lib\site-packages (from stack-data->ipython>=7.23.1->ipykernel) (2.0.5)

info 13:53:41.854: Requirement already satisfied: pure-eval in c:\python310\lib\site-packages (from stack-data->ipython>=7.23.1->ipykernel) (0.2.2)

info 13:53:41.913: Installing collected packages: ipykernel

info 13:53:42.3: ERROR: Could not install packages due to an OSError: [WinError 5] Access is denied: 'c:\Python310\share'
Consider using the --user option or check the permissions.

info 13:53:42.11: WARNING: You are using pip version 22.0.4; however, version 22.1.2 is available.
You should consider upgrading via the 'c:\Python310\python.exe -m pip install --upgrade pip' command.

error 13:53:42.145: Failed to install ipykernel WARNING: You are using pip version 22.0.4; however, version 22.1.2 is available.
You should consider upgrading via the 'c:\Python310\python.exe -m pip install --upgrade pip' command.

info 13:53:42.147: Dispose Kernel 'Untitled-1.ipynb' associated with 'Untitled-1.ipynb'
error 13:53:42.150: Error in execution [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
error 13:53:42.151: Error in execution (get message for cell) [KernelProcessExitedError: The kernel died. Error: c:\Python310\python.exe: No module named ipykernel_launcher... View Jupyter log for further details.
at ChildProcess. (c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\out\kernels\raw\launcher\kernelProcess.node.js:122:33)
at ChildProcess.emit (node:events:402:35)
at Process.onexit (node:internal/child_process:290:12)
at Process.callbackTrampoline (node:internal/async_hooks:130:17)] {
category: 'kerneldied',
kernelConnectionMetadata: {
kind: 'startUsingPythonInterpreter',
kernelSpec: {
specFile: 'c:\Users\t-mlively\Documents\Jupyter_Extension_Workspace\vscode-jupyter\temp\jupyter\kernels\python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c\kernel.json',
interpreterPath: 'c:\Python310\python.exe',
isRegisteredByVSC: 'registeredByNewVersionOfExt',
name: 'python3105jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c',
argv: [Array],
language: 'python',
executable: 'python',
display_name: 'Python 3.10.5 64-bit',
metadata: [Object],
env: {}
},
interpreter: {
id: 'C:\PYTHON310\PYTHON.EXE',
sysPrefix: 'C:\Python310',
envType: 'Global',
envName: '',
architecture: 3,
sysVersion: '3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]',
version: [Object],
companyDisplayName: 'PythonCore',
displayName: 'Python 3.10.5 64-bit',
detailedDisplayName: 'Python 3.10.5 64-bit',
uri: [p]
},
id: '.jvsc74a57bd0369f2c481f4da34e4445cda3fffd2e751bd1c4d706f27375911949ba6bb62e1c.c:\Python310\python.exe.c:\Python310\python.exe.-m#ipykernel_launcher'
},
exitCode: 1,
stdErr: 'c:\Python310\python.exe: No module named ipykernel_launcher\r\n'
}
info 13:53:42.190: Process Execution: > c:\Python310\python.exe -c "import ipykernel"

c:\Python310\python.exe -c "import ipykernel"

@github-actions github-actions bot added the triage-needed Issue needs to be triaged label Jun 16, 2022
@IanMatthewHuff
Copy link
Member

Pulling out the relevant error here from the larger log:

info 13:48:41.466: Installing collected packages: ipython, ipykernel

info 13:48:41.780: ERROR: Could not install packages due to an OSError: [WinError 5] Access is denied: 'c:\Python310\share'
Consider using the --user option or check the permissions.

@IanMatthewHuff IanMatthewHuff removed their assignment Jun 16, 2022
@rchiodo rchiodo added kernel-crash bug Issue identified by VS Code Team member as probable bug and removed triage-needed Issue needs to be triaged labels Jun 23, 2022
@DonJayamanne DonJayamanne self-assigned this Aug 11, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug notebook-getting-started
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants