[Numpy-discussion] Sources more confusing in Python
Sun Apr 7 16:49:25 CDT 2013
> On Sun, Apr 7, 2013 at 5:34 PM, Steve Waterbury <firstname.lastname@example.org>
> > On 04/07/2013 05:30 PM, Nathaniel Smith wrote:
> >> On Sun, Apr 7, 2013 at 10:25 PM, Steve Waterbury
> >> <email@example.com> wrote:
> >>> On 04/07/2013 05:02 PM, Chris Barker - NOAA Federal wrote:
> >>>> On Sun, Apr 7, 2013 at 8:06 AM, Daπid <firstname.lastname@example.org> wrote:
> >>>>> On 7 April 2013 16:53, Happyman <email@example.com> wrote:
> >>>>> $pip install numpy # to install package "numpy"
> >>>> as a warning, last I checked pip did not support binary installs ...
> >>> Guess you didn't check very recently ;) -- pip does indeed
> >>> support binary installs.
> >> Binary install in this case means, downloading a pre-built package
> >> containing .so/.dll files -- very useful if you don't have a working C
> >> compiler environment on the system you're installing onto.
> > Point taken -- just didn't want pip to be sold short.
> > I'm one of those spoiled Linux people, obviously ... ;)
> However, pip is really awful on Windows.
> If you have a virtualenv and you use --upgrade, it wants to upgrade all
> package dependencies (!), but it doesn't know how (with numpy and scipy).
> (easy_install was so much nicer.)
You can use --no-deps to prevent pip from trying to upgrade dependencies.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion