Open andrew-polk opened 1 year ago
Ah. If I run the installer with admin permissions, I get the C:\Python37-32
directory and everything works.
It seems this is a regression from the installer which had python 2.7.
Unfortunately, we have lost contact with the volunteer who was supporting this.
Do the app builders still point to this repo for installing aeneas? If what I've described is a general problem, it seems like it would be biting Windows users all the time.
Do the app builders still point to this repo for installing aeneas?
I've answered my own question. The docs point people to https://software.sil.org/readingappbuilder/download/ which has both the old python 2 installer as well as the python 3 installer. But the python 2 installer is listed first, so maybe most users just end up with the working installer by default.
I'm still here. The developer of aeneas isn't doing any more work on it anymore, so I haven't had anything motivating me to update the AIO installer. Python 2.7 has reached end of life so the Python 3 installer (which was more on the lines of experimental for my part) probably should be the preferred installer now (plus a note to install with administrative permissions). I will try to get a new Python 3 installer built sometime.
@danielbair part of the problem is this major change was introduced without so much as a patch number increase. Because of the problems that change is making, we would like to point our users to the version they need to download. So one idea is just to fix the numbering; we could remove some of these releases and re-label current release as "1.8". Then we could tell our users that Bloom works with 1.7.
While we're discussing this, as damage control, I will see about adding a message that Admin permissions are now required to all Python 3 releases.
I'm not certain about going from 1.7 to 1.8 (I'm trying to keep the version in-sync with the aeneas versions), but I do have the latest versions marked with a revision like this v1.7.3.0_4 (I hope that helps).
I just uploaded v1.7.3.0_4 signed and notarized for Mac, but I am not able to sign the Windows installer.
Can someone test the latest windows installer and see if it fixes this issue.
Hi, @danielbair
I only heard of Aeneas earlier this evening in a discussion of an issue on Gentle's issue tracker. Thank you for your efforts to simplify setup for Windows users.
I just downloaded and ran aeneas-win64-setup-1.7.3.0_4.exe tonight from https://github.com/sillsdev/aeneas-installer/releases/tag/v1.7.3.0_4 however I had the same issue as described above where Python automatically installs to a location (in my case C:\Program Files\Python39\
) different to where the rest of the installer tries to call it from to complete setup.
When first trying the installer, I just ran it as a normal user and the installer looked for Python 3.9 in C:\Python39\
where it is not to be found on my machine.
After reading the above thread, I tried running the installer again as Administrator and got basically the same error, although it appears to now be looking for Python 3.9 in the correct directory in Program Files.
For whatever reason, when I checked the Scripts folder within C:\Program Files\Python39\
it is completely empty. There is no pip.exe (nor anything else) found.
For this reason, I get the Setup error dialog pictured above when trying to install:
Finally, this is briefly shown prior to the termination of the installer.
The installer then reports that everything has been installed, although that is clearly not the case.
Any further direction would be appreciated.
The installer is putting python in
C:\Users\UserName\AppData\Local\Programs\Python\Python37-32
but everything in the rest of the package expects python to be atC:\Python37-32
so nothing works after that.Any ideas what is different in my setup?