Eryk Sun added the comment:
> The default association should go to pyw.exe, which is likely in
> your C:\Windows directory.
However, don't browse for pyw.exe. That will create a new progid that doesn't
support command-line arguments or a shell drop handler. You should select the
Python app
Steve Dower added the comment:
> it fails with this error means you're running a virtual-environment launcher
> instead of a base Python executable.
Exactly. It sounds like you probably searched for pythonw.exe and found the one
in Lib/venv/scripts/nt instead of the actual one.
The default
Eryk Sun added the comment:
> "Python Launcher is sorry to say... No pyvenv.cfg file"
As already mentioned, that it fails with this error means you're running a
virtual-environment launcher instead of a base Python executable. That it
displays a message box means you ran a GUI pythonw.exe
Chuck added the comment:
Does anyone know why when Python Launcher is executed by double clicking on the
Python script called ecrypt_bitcoinj_seed.pyw a small window pops of stating...
"Python Launcher is sorry to say... No pyvenv.cfg file" as in the image? Why
wouldn't the pyvenv.cfg file
Chuck added the comment:
Mr. Dower, I apologize for not being more specific... since this is Windows
based and not console driven, the file used for execution should be pythonw.exe
according to the instructions at
https://github.com/gurnec/decrypt_bitcoinj_seed so I right clicked on
Steve Dower added the comment:
It seems like you're trying to launch the python.exe that is created for a
virtual environment rather than the actual one. This probably means that at
some point you created a virtual environment and updated your file association
to launch it.
The best thing
New submission from Chuck :
on Windows 10 64 after install of Python 3.8.5 and after install of
decrypt_bitcoinj_seed.pyw <--- and after double click, I get "Python Launcher
is sorry to say... No pyvenv.cfg file". I have tried multiple reinstalls of
Python to no avail. When a search is
