moin icon indicating copy to clipboard operation
moin copied to clipboard

"python quickinstall.py" does not install entire venv

Open RogerHaase opened this issue 2 years ago • 2 comments

On windows 10, deleting the venv and the "m.bat" file and executing

py -3 quickinstall.py

used to install the whole venv (with the exception of "extras"), but now the log output says:

'pip' is not recognized as an internal or external command,
operable program or batch file.
'tox' is not recognized as an internal or external command,
operable program or batch file.

Now I must do additional commands:

activate
pip install tox
pip install wheel
m quickinstall
m extras

RogerHaase avatar Jul 05 '22 21:07 RogerHaase

I might need some help reproducing this error: After completely installing Moin2, then deleting the moin-venv-python folder (and all subfolders) (on Windows 10) and then running py -3 quickinstall.py does not lead to any errors for me.

Do I need to manually uninstall pip and/or tox beforehand to reproduce the error or might this simply be already fixed?

JanHoefelmeyer avatar Aug 08 '22 12:08 JanHoefelmeyer

Forgot to add """venv and the "m.bat" file""" in the original issue description. Optionally "activate.bat" and "deactivate.bat" can be deleted to get closer to the state after a fresh clone.

Updated the original issue.

RogerHaase avatar Aug 08 '22 14:08 RogerHaase

I'm still unable to reproduce this issue. I've uninstalled tox and wheel even and only get a warning for wheel, although the wiki can still be used normally after this. I've set up completely fresh clones of moin2 (while uninstalling tox and wheel) as well with no success.

Only way I could reproduce something was by uninstalling pip, which caused the log to be 'pip' is not recognized as an internal or external command, operable program or batch file..

Since pip is (along with Python 3.8+) given as required in the docs for quickinstall.py I doubt that this is related to the problem, or a problem in the first place. Does this issue maybe require another retest?

JanHoefelmeyer avatar Aug 16 '22 05:08 JanHoefelmeyer

Thanks for trying to reproduce. It was a "User Error".

The problem was "resolved" by adding .../Python310 to the environmental path. When I checked the path value, I discovered the only Python in the path was a pointer to Python 3.8 which was removed several months ago.

When installing Python 3.10, I missed checking the "Add Python 3.10 to Path" checkbox. Thanks for your help.

RogerHaase avatar Aug 17 '22 17:08 RogerHaase