OpenEnergyPlatform / OpenEnergyPlatform/academy

jupyter notebooks kernel runs correctly

Open
#82 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
20
Forks
9
PR merge metrics
No merged PRs in 30d

Description

After installation with the requirements.yml file for the API and manually installing jupyter notebook in the environment I ran the first tutorial notebook but its kernel fails as shown below.

Traceback (most recent call last):
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\web.py", line 1592, in _execute
result = yield result
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 1133, in run
value = future.result()
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\asyncio\futures.py", line 294, in result
raise self._exception
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 1141, in run
yielded = self.gen.throw(*exc_info)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\notebook\services\sessions\handlers.py", line 73, in post
type=mtype))
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 1133, in run
value = future.result()
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\asyncio\futures.py", line 294, in result
raise self._exception
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 1141, in run
yielded = self.gen.throw(*exc_info)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\notebook\services\sessions\sessionmanager.py", line 79, in create_session
kernel_id = yield self.start_kernel_for_session(session_id, path, name, type, kernel_name)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 1133, in run
value = future.result()
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\asyncio\futures.py", line 294, in result
raise self._exception
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 1141, in run
yielded = self.gen.throw(*exc_info)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\notebook\services\sessions\sessionmanager.py", line 92, in start_kernel_for_session
self.kernel_manager.start_kernel(path=kernel_path, kernel_name=kernel_name)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 1133, in run
value = future.result()
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\asyncio\futures.py", line 294, in result
raise self._exception
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\tornado\gen.py", line 326, in wrapper
yielded = next(result)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\notebook\services\kernels\kernelmanager.py", line 160, in start_kernel
super(MappingKernelManager, self).start_kernel(**kwargs)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\jupyter_client\multikernelmanager.py", line 110, in start_kernel
km.start_kernel(**kwargs)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\jupyter_client\manager.py", line 240, in start_kernel
self.write_connection_file()
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\jupyter_client\connect.py", line 547, in write_connection_file
kernel_name=self.kernel_name
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\jupyter_client\connect.py", line 212, in write_connection_file
with secure_write(fname) as f:
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\contextlib.py", line 59, in enter
return next(self.gen)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\jupyter_client\connect.py", line 100, in secure_write
win32_restrict_file_to_user(fname)
File "C:\Users\wulf_ni.conda\envs\oep-api\lib\site-packages\jupyter_client\connect.py", line 53, in win32_restrict_file_to_user
import win32api
ImportError: No module named 'win32api'

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with requirements.yml and the first tutorial notebook, then reproduce the kernel startup failure on Windows. Investigate the traceback's missing win32api dependency and verify that the notebook kernel starts successfully in the documented environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.