lektor: Installer broken with virtualenv 20.x
I tried installing Lektor on Linux via the installer script at https://www.getlektor.com/install.sh
. This resulted in the following error messages:
/usr/bin/python: can't open file './src/virtualenv.py': [Errno 2] No such file or directory
/usr/bin/python: can't open file './virtualenv.py': [Errno 2] No such file or directory
It seems the internal structure of the virtualenv
package changed again. If I modify the installer script to force an older version of virtualenv, it works again:
VENV_URL = "https://pypi.org/pypi/virtualenv/16.7.9/json"
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 5
- Comments: 29 (17 by maintainers)
Commits related to this issue
- Merge pull request #298 from lektor/unified-installer Unified installer closes lektor/lektor#720 closes lektor/lektor#635 closes #267 — committed to lektor/lektor-website by xlotlu 4 years ago
- Merge pull request #298 from lektor/unified-installer Unified installer closes lektor/lektor#720 closes lektor/lektor#635 closes #267 — committed to lektor/lektor by xlotlu 4 years ago
- Merge pull request lektor-website/#298 from lektor/unified-installer Unified installer closes lektor/lektor#720 closes lektor/lektor#635 closes lektor-website/#267 — committed to lektor/lektor by xlotlu 4 years ago
- Merge pull request lektor-website/298 from lektor/unified-installer Unified installer closes lektor/lektor#720 closes lektor/lektor#635 closes lektor-website/267 — committed to lektor/lektor by xlotlu 4 years ago
I’ll do it.
No reason except I am more familiar with wget. Here is curl version:
Here is simple urlretrieve version also but it does not show download progress (for that it will be more complicated to solve python2/3 comaptibility issues):
I just tested this with python2 so I am not sure is it working with python3
IIRC virtualenv only ever blew up because they changed the location of the executable. That won’t be a problem with a zipapp.
That’s two branches of code, then there would need to be that pinning logic and procedure… not worth it since the zipapp is the official bootstrap method and that’s the official URL. So yeah, I changed my opinion, sorry for the noise. I think we should go forward with the zipapp way and forget about legacy.
That would be nice.