GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — wppm --register fails in WinPython 3.14.5 · winpython/winpython · Discussion #2043

wppm --register fails in WinPython 3.14.5 #2043

Unanswered
floatmast-cloud asked this question in Q&A
wppm --register fails in WinPython 3.14.5 #2043
@floatmast-cloud floatmast-cloud
Jun 5, 2026 · 1 comment
Return to top
Discussion options

    • Uh oh!

    There was an error while loading. Please reload this page.

floatmast-cloud
Jun 5, 2026

Hi to all !

Any ideas why wppm fails in this WinPython version?

C:\Users\user1>"C:\PortableApps\WPy64-31450\python\Scripts\wppm.exe" --register --verbose
Register WinPython: associate file extensions, icons and context menu with this WinPython
registering C:\PortableApps\WPy64-31450\python
continue ? Y/N
Y
Traceback (most recent call last):
File "", line 203, in _run_module_as_main
File "", line 88, in run_code
File "C:\PortableApps\WPy64-31450\python\Scripts\wppm.exe_main.py", line 5, in
sys.exit(main())
~~~~^^
File "C:\PortableApps\WPy64-31450\python\Lib\site-packages\wppm\wppm.py", line 343, in main
import associate
ModuleNotFoundError: No module named 'associate'

C:\Users\user1>
You must be logged in to vote
All reactions

Replies: 1 comment

Comment options

    • Uh oh!

    There was an error while loading. Please reload this page.

gistrec
Jul 2, 2026

This is a bug in the wppm package rather than something in your setup. The --register code path in wppm/wppm.py does a bare import associate (line 343 — exactly where your traceback points), but associate.py lives inside the wppm package, so Python looks for a top-level associate module and fails. Every other import in that file already uses the relative form (from . import utils, ...); the two import associate lines under --register/--unregister just weren't updated when wppm became an installable package.

Until it's fixed you can call the module directly:

"C:\PortableApps\WPy64-31450\python\python.exe" -c "from wppm import associate; associate.register(r'C:\PortableApps\WPy64-31450\python', verbose=True)"

Worth filing as an issue — the fix is changing import associate to from . import associate at both spots in wppm/wppm.py.
You must be logged in to vote
All reactions
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
2 participants
@floatmast-cloud @gistrec
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.