<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
While I like the concept of calling pip via an api (and let me pat
myself on the back for suggesting it in the first place in this
thread), I honestly think that if it is something that is allowed,
it should be implemented with a fair bit of guards. It would
probably end up being a power-user feature - something to help
manage deployments in some tricky environments - than a newbie
feature.<br>
<br>
Python is an IDE-less language, and I say this knowing full well
what IDLE is. We don't default to eclipse like java does, or Visual
Studio like .NET languages (and C(++) on windows). We do not have
the default tooling in place to avoid using the command line.
Learning the command line is a vital skill for newbies.<br>
<br>
Now, while this thread may or may not be about Windows newbies
specifically, I do not tend to see this brought up for *nix
newbies. Is this because we assume that a *nix user will have to
know the command line? or that they are inherently power users? If
it is the latter, then I need to say that being a programmer also
means being a power user. We should guide new users to power user
tools (the command line, powershell, etc), instead of trying to bend
python to regular users who will eventually be power users anyways.<br>
<br>
I guess I am suggesting maybe we try and find a way to shallow the
learning curve into using the command line than to just implement
commands in the repl itself.<br>
<br>
all that said, IDLE could be tooled to intercept the syntax 'pip
install foo' and print a more helpful message.<br>
<br>
<div class="moz-cite-prefix">On 11/13/2015 15:27, Chris Barker
wrote:<br>
</div>
<blockquote
cite="mid:CALGmxE+JhOZzXAOE3NHV0s-f849dDjrMGTzb=4N99LSczyrwNQ@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Nov 13, 2015 at 12:09 PM,
Nathaniel Smith <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:njs@pobox.com"
target="_blank">njs@pobox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span
class="">
<p dir="ltr">On Nov 13, 2015 12:00 PM, "Alexander
Walters" <<a moz-do-not-send="true"
href="mailto:tritium-list@sdamon.com"
target="_blank">tritium-list@sdamon.com</a>>
wrote:<br>
><br>
> import pip<br>
> pip.install(PACKAGESPEC)<br>
><br>
> something like that?</p>
</span>
<p dir="ltr">This would be extremely handy if it could be
made to work reliably... But I'm skeptical about whether
it can be made to work reliably. Consider all the fun
things that could happen once you start upgrading
packages while python is running, and might e.g. have
half of an upgraded package already loaded into memory.
It's like the reloading problem but even more so.</p>
</blockquote>
<div>indeed -- does seem risky.</div>
<div><br>
</div>
<div>also, if were are in fantasy land, and want to be
really newbie friendly, a new built in:</div>
<div><br>
</div>
<div>pip.install(PACKAGESPEC)<br>
</div>
<div><br>
</div>
<div>with no import required....</div>
<div><br>
</div>
<div>-CHB</div>
<div><br>
</div>
</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature"><br>
Christopher Barker, Ph.D.<br>
Oceanographer<br>
<br>
Emergency Response Division<br>
NOAA/NOS/OR&R (206) 526-6959 voice<br>
7600 Sand Point Way NE (206) 526-6329 fax<br>
Seattle, WA 98115 (206) 526-6317 main reception<br>
<br>
<a moz-do-not-send="true"
href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</div>
</div>
</blockquote>
<br>
</body>
</html>