[Numpy-discussion] "official" binaries on web page.
matthew.brett at gmail.com
Wed Oct 23 13:10:21 EDT 2013
On Wed, Oct 23, 2013 at 8:16 AM, jim vickroy <jim.vickroy at noaa.gov> wrote:
> On 10/23/2013 8:51 AM, Chris Barker - NOAA Federal wrote:
> Ralf Gommers <ralf.gommers at gmail.com> wrote:
> but the layout of that page is on
> purpose. scipy.org is split into two parts: (a) a SciPy Stack part, and
> a numpy & scipy library part. You're looking at the stack part, and the
> preferred method to install that stack is a Python distribution.
> OK, I'm not sure that's a great idea, but if we take that as a given:
> That page could use some clarification about what the heck the "stack"
> is, and what its relationship to the scipy and numpy packages is.
> And I still think it wouldn't hurt to more obviously point people to
> how to get either numpy or scipy themselves.
> So maybe my section about the "official" binaries, but lower on the
> page. I don't like "custom" as a title, as that makes it sound like
> advanced numpy-fu, not where a newbie looking for just numpy is going
> to look.
> But it sounds like the real problem is with the surrounding
> pages--that's the page you find when you try to figure out how to get
> numpy--if that page is about the stack, it should not be linked to
> directly from the numpy.org page without explanation.
> We do have a branding problem: "scipy" is a package, a "stack" and a
> ecosystem/community. It should be clear which one is being referred to
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> Chris, thanks for taking this on! You very clearly state all of the
> confusion I have had with Numpy and Scipy distributions and branding. I
> also agree that relying on a Python distribution to provide Scipy and Numpy
> is not a good idea. --jv
I know what you mean.
I think there are two groups of users out there:
1) Want software, want it now, with minimum fuss; no beef with
installer being primarily based at a single company
2) Like to know how everything got onto my computer, strong preference
for community-supported distributions
I guess that there's a fairly large group 2 in the Python community.
For me, that was a powerful reason to switch from MATLAB. Some of
this group is just starting, they own Macs or have Windows machines,
and they need binary installers.
I don't think there's any practical way of shifting people between
groups, and trying to do so will likely cause heated arguments.
There's no need to prefer one group over the other - we just need to
make sure that both groups have instructions and binaries they can
recognize as being for their case. As in:
(Group 1): The easiest way to get ....
(Group 2): You can also install the stack from community-supported
binaries, this is more complicated, but possible by ...
More information about the NumPy-Discussion