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 loewis
Recipients BreamoreBoy, ellipso, eryksun, loewis, ned.deily, peter@psantoro.net, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2014-06-22.17:44:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403459092.8.0.649220967752.issue21427@psf.upfronthosting.co.za>
In-reply-to
Content
Peter: as it turns out, Uwe actually reported two separate issue. In this tracker, we have a "one issue at a time policy", and I'm relabelling the issue as the one that Uwe initially reported (cannot register 64bit component).

So I'm quite certain that *your* (Peter's) issue is not the same as the one reported here. Please report it in a separate issue. People following up to this, please only follow-up if you want to contribute to the original problem (namely, "cannot register 64 bit component").

Uwe: thanks for your investigation. I understand that the problem you were concerned about (installation failed) is solved with a work-around. If you want to see it properly resolved/investigated, please submit a new bug report, providing detailed steps to reproduce the issue. 

Without such steps, I'm tempted to declare that this was a problem with a third-party library, and not a problem with Python, or a misconfiguration of your machine. It is not plausible that the 3.4 installation would access the 3.3 installation directory, so if it did, it's either because some extension library, or some system administrator, has messed with the configuration (registry or environment variables).
History
Date User Action Args
2014-06-22 17:44:52loewissetrecipients: + loewis, terry.reedy, tim.golden, ned.deily, BreamoreBoy, zach.ware, eryksun, steve.dower, peter@psantoro.net, ellipso
2014-06-22 17:44:52loewissetmessageid: <1403459092.8.0.649220967752.issue21427@psf.upfronthosting.co.za>
2014-06-22 17:44:52loewislinkissue21427 messages
2014-06-22 17:44:52loewiscreate