Opened 6 years ago

Closed 4 years ago

#3794 enhancement closed wontfix (wontfix)

Increase verbosity of Windows installer initalize message.

Reported by: verm Owned by:
Priority: normal Milestone:
Component: core Keywords: installer
Cc: jessica.mckellar@…, thijs Branch:
Author: Launchpad Bug:

Description

The Windows installer can be very unhelpful in it's error message in trunk/win32/pyx.x-foo.iss.template -> InitalizeSetup

"Python does not appear to be installed"
"Please install Python before attempting to install Twisted."

The actual Error was Python2.5 amd64 was installed when the 32bit version is required. It would be nice to have a few extra checks here for such cases as situations like these when there is no way to debug the actual error can result in many hours of wasted time.

Change History (14)

comment:1 Changed 5 years ago by glyph

  • Owner changed from glyph to verm

comment:2 follow-up: Changed 5 years ago by kleist

I get the same error message with "Twisted_NoDocs-8.2.0.win32-py2.6.exe" on 64 bit Windows 7 with Python 2.6/amd64.

It would be very helpful if the download page clearly stated that a 32 bit Python installation is required. Or mentioned at http://twistedmatrix.com/trac/wiki/FrequentlyAskedQuestions#Installation

comment:3 in reply to: ↑ 2 Changed 4 years ago by thijs

  • Keywords review added
  • Owner verm deleted

Replying to kleist:

It would be very helpful if the download page clearly stated that a 32 bit Python installation is required. Or mentioned at http://twistedmatrix.com/trac/wiki/FrequentlyAskedQuestions#Installation

I've added a new entry on FrequentlyAskedQuestions, putting it up for review.

comment:4 Changed 4 years ago by jesstess

  • Cc jessica.mckellar@… added
  • Keywords review removed
  • Owner set to thijs

Thanks for working on this, thijs. The FAQ answer looks fine.

The ticket asks for a better installer message, though. Is checking the bit-edness of a Python installation on Windows hard enough that an FAQ entry is the best we'll likely do?

comment:5 Changed 4 years ago by thijs

  • Cc thijs added
  • Owner changed from thijs to therve

I'm not sure, but that sounds like a good plan, reassigning it to therve that creates the win installers afaik.

comment:6 Changed 4 years ago by therve

We're not using the installer anymore?

comment:7 Changed 4 years ago by exarkun

Right. We're generating them with bdist_wininst and bdist_msi. So someone should request this additional checking in distutils (upstream), if it's still a problem.

comment:8 Changed 4 years ago by thijs

Looks like we need to generate separate installers for 32-bit and 64-bit windows as described in the distutils documentation. This is only supported for Python 2.6 and newer though.

comment:9 Changed 4 years ago by exarkun

So one of the Windows slave needs a 64-bit Python install.

comment:10 follow-up: Changed 4 years ago by verm

Well, at the very least could the error message be changed to note that a 32bit python is required? "Please install a 32bit Python..." or something similar? That would go a long way until a proper fix is found.

comment:11 in reply to: ↑ 10 ; follow-up: Changed 4 years ago by therve

Replying to verm:

Well, at the very least could the error message be changed to note that a 32bit python is required? "Please install a 32bit Python..." or something similar? That would go a long way until a proper fix is found.

Are you talking about something happening with the MSI installers? The ISS template is not used anymore, so we can't change the message you're seeing.

comment:12 in reply to: ↑ 11 Changed 4 years ago by verm

Replying to therve:

Replying to verm:

Well, at the very least could the error message be changed to note that a 32bit python is required? "Please install a 32bit Python..." or something similar? That would go a long way until a proper fix is found.

Are you talking about something happening with the MSI installers? The ISS template is not used anymore, so we can't change the message you're seeing.

Well, I haven't tested this issue since then however it's been 19 months. If the specific issue I was discussing about a less-than-useful error message when encountering a 32/64bit jabber between required versions if this has been fixed the ticket can be closed.

comment:13 Changed 4 years ago by therve

  • Resolution set to wontfix
  • Status changed from new to closed

OK, thanks.

comment:14 Changed 4 years ago by <automation>

  • Owner therve deleted
Note: See TracTickets for help on using tickets.