Skip to content

Startup of CNApy 1.2.9 fails on Windows 11 #575

Closed

Description

@doserm

Describe the bug
Fresh Windows install of 1.2.9 via install_cnapy_here.bat fails at startup with ModuleNotFoundError: No module named 'nest_asyncio'

To Reproduce
Steps to reproduce the behavior:

  1. Install CNApy 1.2.9 via the windows installer
  2. execute RUN_CNApy.bat from the terminal to reproduce the error

Expected behavior
Startup of the GUI

Screenshots
If applicable, add screenshots to help explain your problem.

Please complete the following information:

  • OS: Windows 11
  • Python 3.10.22

Additional context
Error Message:
C:\Users\user\CNApy\cnapy-1.2.9>powershell -NoProfile -ExecutionPolicy Bypass -File "C:\Users\user\CNApy\cnapy-1.2.9\cnapy_runner_helper.ps1"
Traceback (most recent call last):
File "C:\Users\user\CNApy\cnapy-1.2.9\cnapy-environment\lib\runpy.py", line 196, in _run_module_as_main
return run_code(code, main_globals, None,
File "C:\Users\user\CNApy\cnapy-1.2.9\cnapy-environment\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "C:\Users\user\CNApy\cnapy-1.2.9\cnapy-environment\Scripts\cnapy.exe_main
.py", line 4, in
File "C:\Users\user\CNApy\cnapy-1.2.9\cnapy-environment\lib\site-packages\cnapy_main
.py", line 32, in
from cnapy.application import Application
File "C:\Users\user\CNApy\cnapy-1.2.9\cnapy-environment\lib\site-packages\cnapy\application.py", line 32, in
import nest_asyncio
ModuleNotFoundError: No module named 'nest_asyncio'

Workaround:
<install-dir>\cnapy-1.2.9\cnapy-environment\python.exe -m pip install nest_asyncio
CNApy then starts normally.

Activity

  1. sunxiuguo commented on Oct 28, 2026

    @sunxiuguo

    I checked the published cnapy-1.2.9-py3-none-any.whl against its PyPI SHA-256 (064784547f3f3bedbdbbc63e4adf03347ee955de9c510355f21f5e51239e1294): cnapy/application.py imports nest_asyncio, but the wheel's 20 direct Requires-Dist entries omit nest-asyncio. This is package-metadata validation, not a Windows GUI or full dependency-resolution test.

    The current Windows installer uses uv pip install cnapy, so the declaration in environment.yml does not cover that installation path. There is already related work: #563 included the dependency but closed unmerged; the open #574 instead changes both the import and dependency to nest_asyncio2.

    Would a narrowly scoped 1.x dependency-metadata hotfix be useful while #574 is pending, or should this wait for that migration? I have not opened a competing patch. AI-assisted investigation.

  2. added a commit that references this issue on Oct 29, 2026
  3. Paulocracy commented on Oct 29, 2026

    @Paulocracy
    Member

    Thank you for raising this issue :D It should be solved now with the hotfix release 1.2.10, if not, please reopen this issue or open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions