This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ellipso
Recipients BreamoreBoy, ellipso, eryksun, loewis, ned.deily, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2014-06-15.09:23:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402824240.0.0.597898866944.issue21427@psf.upfronthosting.co.za>
In-reply-to
Content
problem is solved

observation
- installer problem only occurred on win7 32 bit with prior python installation
(my working system)
- When repeating the installer problem I noticed that a window was opened very shortly with python.exe running. An error message from this call resulted in the exit process of the installer
- the window popped up only for about 1second. A was reading (taking a video) that it was complaining about an error in numpy when calling imp.py in /python33/lib (the old installation, something wrong with libtool, bootstrap)
- I removed step by step all installed libraries, but the error still appeared
- I removed the prior python 3.3.5 installation completely, now the installer worked
- when opening the window with python, it was downloading something like setuptools (not absolutely sure about the name)
- a test with nose 1.3.3, numpy 1.8.1, scipy 0.14.0 (all from Gohlkes web site) went ok.
- unfortunately, the error message with the registry was not reflecting the problem

Hence, the solution is to remove the prior installation of python. That was not necessary in older versions and not necessary for win7 64 bit: strange.
History
Date User Action Args
2014-06-15 09:24:00ellipsosetrecipients: + ellipso, loewis, terry.reedy, tim.golden, ned.deily, BreamoreBoy, zach.ware, eryksun, steve.dower
2014-06-15 09:24:00ellipsosetmessageid: <1402824240.0.0.597898866944.issue21427@psf.upfronthosting.co.za>
2014-06-15 09:23:59ellipsolinkissue21427 messages
2014-06-15 09:23:59ellipsocreate