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 terry.reedy
Recipients lorenzogotuned, terry.reedy, upendra-k14
Date 2016-06-11.04:43:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465620188.08.0.778748885228.issue27051@psf.upfronthosting.co.za>
In-reply-to
Content
sys.executable has the path to the current executable.  But you don't even need that.  When you import pip, it gets that itself to find site-packages.

You are making this way too complicated and are trying to do what pip can do. I don't see that we need to know the system.  Pip does that.  You don't need to know all installed pythons, certainly not to begin.  The first thing is to install to the current version. Expand on that later.  Don't worry about virtual environments.  Beginners don't know what they are, and this is aimed at beginners.

3.6.0a2 will be tagged on Sunday, and I can look at this more after that.
History
Date User Action Args
2016-06-11 04:43:08terry.reedysetrecipients: + terry.reedy, upendra-k14, lorenzogotuned
2016-06-11 04:43:08terry.reedysetmessageid: <1465620188.08.0.778748885228.issue27051@psf.upfronthosting.co.za>
2016-06-11 04:43:08terry.reedylinkissue27051 messages
2016-06-11 04:43:07terry.reedycreate