Python Installer Error

Python
1

Python Installer Error

Trying to install a build of ActivePython 3.8.2 Windows 64-bit and getting an error late in the build process.

There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

Clicking Ok then backs out the installation.

Build includes the following packages.

  • django
  • keras
  • matplotlib
  • numpy
  • pandas
  • py
  • pymysql
  • pymysqldb
  • redis
  • regex
  • scikit-learn
  • scipy
  • sqlalchemy
  • tensorflow
2

Hi markdowd, just to verify, this is the project you are talking about, right?

https://platform.activestate.com/markdowd/Python

Cheers,
Luke

3

Hi @markdowd, I checked with the build team and here’s what they suggested

Add the following packages to your build

  • pypiwin32 223
  • pywin32 227
  • testpath 0.3.1
  • win-unicode-console 0.5

For the Linux build which is failing, they recommended changing numpy to version 1.18.4

Let us know if this works!

Cheers,
Luke

1 Like
4

Worked for Windows, even with the auto-selected testpath 0.4.2, although Linux failed to build so trying that change now.

5

Hey @markdowd - any luck? Let me know if you’re still stuck or if you were able to get a successful build.

6

Hi @flukeout. All sorted, thanks :slight_smile:

3 Likes
7

Hi @markdowd, did you have to do anything other than add the suggested package versions in order to fix your issue? I am having the same install issue on Windows 7 64-bit and this did not fix it for me.

Thanks,
Justin

8

Hi @justin-charron .

Worked as advertised, although there was, perhaps, something else going on for the linux build. I have noticed spurious problems that come and go in the build space.

9

Hi. My name is Mr. Rhee and have a good noon, please.

10

I ran into this same error recently trying to install ActivePython 3.8.8. The issue ended up being that I had a space in my install path, which is apparently a no-go.

This is different than the original problem here, but since this thread seemed to be the most relevant result for this error message, hopefully this can help someone else.