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 bethard
Recipients bethard, loewis, tarek
Date 2009-05-02.20:54:10
SpamBayes Score 7.59132e-12
Marked as misclassified No
Message-id <1241297655.73.0.134067921956.issue5311@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, that was actually easier than I thought it would be. The new patch
introduces properties for each Python version (e.g. TARGETDIR2.4,
PYTHON.MACHINE.2.4, etc.), and disables and hides the features for any
Python versions that aren't found in the registry.

The one remaining issue: What should we do about Python installations
that are missing the appropriate keys in the registry? I imagine this
could happen if, say, you build Python from source. My first thought was
to add an "Other Python Installation" Feature that is disabled (but
visible) by default, and allow the path for that Feature to be filled in
by hand. Does that make sense?
History
Date User Action Args
2009-05-02 20:54:16bethardsetrecipients: + bethard, loewis, tarek
2009-05-02 20:54:15bethardsetmessageid: <1241297655.73.0.134067921956.issue5311@psf.upfronthosting.co.za>
2009-05-02 20:54:14bethardlinkissue5311 messages
2009-05-02 20:54:13bethardcreate