On Mon, Feb 10, 2014 at 11:16 AM, Alexander Belopolsky wrote:
>
> On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
>>
>> On the other hand, it really needs to be deprecated.
>
>
> While numpy.matrix may have its problems, a NEP should list a better
> rationale than the above to gain acceptance.
>
> Pe
Hi,
On Tue, Feb 11, 2014 at 11:40 AM, Pauli Virtanen wrote:
> 11.02.2014 21:20, alex kirjoitti:
> [clip]
>> In the spirit of offsetting this bias and because this thread is
>> lacking in examples of projects that use numpy.matrix, here's another
>> data point: cvxpy (https://github.com/cvxgrp/cvx
11.02.2014 21:20, alex kirjoitti:
[clip]
> In the spirit of offsetting this bias and because this thread is
> lacking in examples of projects that use numpy.matrix, here's another
> data point: cvxpy (https://github.com/cvxgrp/cvxpy) is a serious
> active project that supports the numpy.matrix inte
On Tue, Feb 11, 2014 at 12:05 PM, Matthew Brett wrote:
> Hi,
>
> On Tue, Feb 11, 2014 at 8:55 AM, wrote:
>>
>>
>> On Tue, Feb 11, 2014 at 11:25 AM, Matthew Brett
>> wrote:
>>>
>>> Hi,
>>>
>>> On Tue, Feb 11, 2014 at 4:16 AM, Jacco Hoekstra - LR
>>> wrote:
>>> > For our students, the matrix cla
On Tue, Feb 11, 2014 at 12:14 PM, Chris Barker wrote:
> On Tue, Feb 11, 2014 at 8:25 AM, Matthew Brett
> wrote:
>>
>> > Anyway, I would say that there is a clear use for the matrix class:
>> > readability of linear algebra code and hence a lower chance of errors, so
>> > higher productivity.
>>
>
On Tue, Feb 11, 2014 at 12:14 PM, Chris Barker wrote:
> On Tue, Feb 11, 2014 at 8:25 AM, Matthew Brett wrote:
>
>> > Anyway, I would say that there is a clear use for the matrix class:
>> readability of linear algebra code and hence a lower chance of errors, so
>> higher productivity.
>>
>> Yes, b
On Tue, Feb 11, 2014 at 8:25 AM, Matthew Brett wrote:
> > Anyway, I would say that there is a clear use for the matrix class:
> readability of linear algebra code and hence a lower chance of errors, so
> higher productivity.
>
> Yes, but it looks like there are not any developers on this list who
Hi,
On Tue, Feb 11, 2014 at 8:55 AM, wrote:
>
>
> On Tue, Feb 11, 2014 at 11:25 AM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Tue, Feb 11, 2014 at 4:16 AM, Jacco Hoekstra - LR
>> wrote:
>> > For our students, the matrix class is really appealing as we use a lot
>> > of linear algebra and expre
On Tue, Feb 11, 2014 at 11:25 AM, Matthew Brett wrote:
> Hi,
>
> On Tue, Feb 11, 2014 at 4:16 AM, Jacco Hoekstra - LR
> wrote:
> > For our students, the matrix class is really appealing as we use a lot
> of linear algebra and expressions with matrices simply look better with an
> operator instead
Hi,
On Tue, Feb 11, 2014 at 4:16 AM, Jacco Hoekstra - LR
wrote:
> For our students, the matrix class is really appealing as we use a lot of
> linear algebra and expressions with matrices simply look better with an
> operator instead of a function:
>
> x=A.I*b
>
> looks much better than
On 2/11/2014 5:25 AM, Pauli Virtanen wrote:
> the ndarray is also lacking some useful things, as
> you point out. But I think the right solution would be to stuff
> the required additions into ndarray, rather than retaining the
> otherwise incompatible np.matrix as a crutch.
Given that we now h
Pauli Virtanen wrote:
> [1] http://fperez.org/py4science/numpy-pep225/numpy-pep225.html
I have to agree with Robert Kern here. One operator that we can (ab)use for
matrix multiplication would suffice.
Sturla
___
NumPy-Discussion mailing list
NumPy-Di
dinsdag 11 februari 2014 12:47
To: numpy-discussion@scipy.org
Subject: Re: [Numpy-discussion] deprecate numpy.matrix
Sturla Molden gmail.com> writes:
> Pauli Virtanen iki.fi> wrote:
> > It is not a good thing that there is no well defined "domain
> > specific la
Sturla Molden gmail.com> writes:
> Pauli Virtanen iki.fi> wrote:
> > It is not a good thing that there is no well defined
> > "domain specific language" for matrix algebra in Python.
>
> Perhaps Python should get some new operators?
It might still be possible to advocate for this in core Python
Pauli Virtanen wrote:
> It is not a good thing that there is no well defined
> "domain specific language" for matrix algebra in Python.
Perhaps Python should get some new operators?
__dot__
__cross__
__kronecker__
Obviously, using them in real Python code would require unicode.
;-)
On the se
My 2pc:
I personally hardly ever use matrix, even in linear algebra dense code. It
can be nice though, to use matrix semantics within a restricted scope. When
I first came to numpy, the ability to choose linear algebra versus array
semantics seemed like a really neat thing to me; though in practic
Alan G Isaac gmail.com> writes:
[clip]
> Here, quacking is behaving like an ndarray (in your view,
> as I understand it) when asked. But how do we ask?
> Your view (if I understand) is we ask via the operations
> supported by ndarrays. But maybe that is the wrong way
> for the library to ask thi
On Feb 11, 2014 3:23 AM, "Alan G Isaac" wrote:
>
> On 2/10/2014 7:39 PM, Pauli Virtanen wrote:
> > The issue here is semantics for basic linear algebra operations, such as
> > matrix multiplication, that work for different matrix objects, including
> > ndarrays.
>
>
> I'll see if I can restate my
On 2/10/2014 7:39 PM, Pauli Virtanen wrote:
> The issue here is semantics for basic linear algebra operations, such as
> matrix multiplication, that work for different matrix objects, including
> ndarrays.
I'll see if I can restate my suggestion in another way,
because I do not feel you are respo
On Mon, Feb 10, 2014 at 6:11 PM, Charles R Harris wrote:
>
>
>
> On Mon, Feb 10, 2014 at 5:39 PM, Pauli Virtanen wrote:
>
>> 11.02.2014 01:39, josef.p...@gmail.com kirjoitti:
>> [clip]
>> > Almost all the code in scipy.stats and statsmodels starts with
>> np.asarray.
>> > The numpy doc standard
On Mon, Feb 10, 2014 at 5:39 PM, Pauli Virtanen wrote:
> 11.02.2014 01:39, josef.p...@gmail.com kirjoitti:
> [clip]
> > Almost all the code in scipy.stats and statsmodels starts with
> np.asarray.
> > The numpy doc standard has the term `array_like` to indicate things that
> > can be converted to
11.02.2014 01:39, josef.p...@gmail.com kirjoitti:
[clip]
> Almost all the code in scipy.stats and statsmodels starts with np.asarray.
> The numpy doc standard has the term `array_like` to indicate things that
> can be converted to a usable object by ndasarray.
>
> ducktyping could be restricted to
On Mon, Feb 10, 2014 at 6:39 PM, wrote:
>
>
> On Mon, Feb 10, 2014 at 6:29 PM, Pauli Virtanen wrote:
>
>> 11.02.2014 00:31, Alan G Isaac kirjoitti:
>> > On 2/10/2014 5:11 PM, Pauli Virtanen wrote:
>> >> The existence of np.matrix messes up the general agreement on ndarray
>> >> semantics in Pyth
On Mon, Feb 10, 2014 at 6:29 PM, Pauli Virtanen wrote:
> 11.02.2014 00:31, Alan G Isaac kirjoitti:
> > On 2/10/2014 5:11 PM, Pauli Virtanen wrote:
> >> The existence of np.matrix messes up the general agreement on ndarray
> >> semantics in Python. The meaning of very basic code such as
> >>
> >>
11.02.2014 00:31, Alan G Isaac kirjoitti:
> On 2/10/2014 5:11 PM, Pauli Virtanen wrote:
>> The existence of np.matrix messes up the general agreement on ndarray
>> semantics in Python. The meaning of very basic code such as
>>
>> A * B
>> A.sum(0)
>> A[0]
>>
>> where A and B are NxN
Hi,
On Mon, Feb 10, 2014 at 2:33 PM, Pauli Virtanen wrote:
> 11.02.2014 00:17, Matthew Brett kirjoitti:
> [clip]
>> That is a very convincing argument.
>>
>> What would be the problems (apart from code compatibility) in making
>> scipy.sparse use the ndarray semantics?
>
> I'd estimate the effort
11.02.2014 00:17, Matthew Brett kirjoitti:
[clip]
> That is a very convincing argument.
>
> What would be the problems (apart from code compatibility) in making
> scipy.sparse use the ndarray semantics?
I'd estimate the effort it would take to convert scipy.sparse to ndarray
semantics is about a
On 2/10/2014 5:11 PM, Pauli Virtanen wrote:
> The existence of np.matrix messes up the general agreement on ndarray
> semantics in Python. The meaning of very basic code such as
>
> A * B
> A.sum(0)
> A[0]
>
> where A and B are NxN matrices of some sort now depends on the types
>
Hi,
On Mon, Feb 10, 2014 at 2:11 PM, Pauli Virtanen wrote:
> 10.02.2014 23:40, Alan G Isaac kirjoitti:
>> On 2/10/2014 4:28 PM, Pauli Virtanen wrote:
>>> Starting with asarray won't work: sparse matrices are not
>>> subclasses of ndarray.
>>
>> I was focused on the `matrix` object. For this objec
On Mon, Feb 10, 2014 at 1:13 PM, Alan G Isaac wrote:
> Do you mean one must start out with an 'asarray'?
> Or more than that?
>
maybe np.asanyarray()
It's nice, at least in principle for duck-typed functions to return the
type they were handed. And this really is the primary issu ewith np.matr
On Mon, Feb 10, 2014 at 4:42 PM, Alan G Isaac wrote:
> On 2/10/2014 4:40 PM, alex wrote:
>> I really want to remove it
>
> Can you articulate the problem created by its existence
> that leads you to this view?
In my opinion, Pauli has articulated these problems well in this thread.
__
10.02.2014 23:40, Alan G Isaac kirjoitti:
> On 2/10/2014 4:28 PM, Pauli Virtanen wrote:
>> Starting with asarray won't work: sparse matrices are not
>> subclasses of ndarray.
>
> I was focused on the `matrix` object. For this object, an initial
> asarray is all it takes to use array code. (Or ...
Hi,
On Mon, Feb 10, 2014 at 1:52 PM, Charles R Harris
wrote:
>
>
>
> On Mon, Feb 10, 2014 at 2:28 PM, Pauli Virtanen wrote:
>>
>> 10.02.2014 23:13, Alan G Isaac kirjoitti:
>> > On 2/10/2014 4:03 PM, Pauli Virtanen wrote:
>> >> What sparked this discussion (on Github) is that it is not
>> >> poss
On Mon, Feb 10, 2014 at 2:28 PM, Pauli Virtanen wrote:
> 10.02.2014 23:13, Alan G Isaac kirjoitti:
> > On 2/10/2014 4:03 PM, Pauli Virtanen wrote:
> >> What sparked this discussion (on Github) is that it is not
> >> possible to write duck-typed code that works correctly for:
> >
> > Do you mean o
On 2/10/2014 4:40 PM, alex wrote:
> I really want to remove it
Can you articulate the problem created by its existence
that leads you to this view?
Alan Isaac
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/l
On Mon, Feb 10, 2014 at 3:47 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Feb 10, 2014 at 12:44 PM, Charles R Harris
> wrote:
>>
>>
>>
>> On Mon, Feb 10, 2014 at 1:23 PM, Alan G Isaac wrote:
>>>
>>> On 2/10/2014 3:04 PM, Matthew Brett wrote:
>>> > I teach psychologists and neuroscientists mainly
>
On 2/10/2014 4:28 PM, Pauli Virtanen wrote:
> Starting with asarray won't work: sparse matrices are not subclasses
> of ndarray.
I was focused on the `matrix` object.
For this object, an initial asarray is all it takes to use array code.
(Or ... not?) And it is a view, not a copy.
I don't have
10.02.2014 23:13, Alan G Isaac kirjoitti:
> On 2/10/2014 4:03 PM, Pauli Virtanen wrote:
>> What sparked this discussion (on Github) is that it is not
>> possible to write duck-typed code that works correctly for:
>
> Do you mean one must start out with an 'asarray'? Or more than
> that?
Starting
On 2/10/2014 4:08 PM, Matthew Brett wrote:
> I think the active questions here are:
> * Should we collect the discussion in coherent form somewhere?
> * Should we add something to the np.matrix docstring and if so what?
> * (Pauli's point): to what extent should we try to emulate the np.matrix API.
On 2/10/2014 4:03 PM, Pauli Virtanen wrote:
> What sparked this discussion (on Github) is that it is not possible to
> write duck-typed code that works correctly for:
Do you mean one must start out with an 'asarray'?
Or more than that?
As I detailed in past discussion, the one thing
I really do n
Hi,
On Mon, Feb 10, 2014 at 12:58 PM, wrote:
>
>
> On Mon, Feb 10, 2014 at 3:45 PM, alex wrote:
>>
>> On Mon, Feb 10, 2014 at 2:36 PM, Matthew Brett
>> wrote:
>> > Hi,
>> >
>> > On Mon, Feb 10, 2014 at 6:26 AM, Nathaniel Smith wrote:
>> >> On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
>> >>> H
10.02.2014 22:23, Alan G Isaac kirjoitti:
[clip]
> As far as I have been able to discern, the underlying
> motivation for eliminating the matrix class is that
> some developers want to stop supporting in any form
> the subclassing of numpy arrays. Do I have that right?
What sparked this discussio
On Mon, Feb 10, 2014 at 3:39 PM, wrote:
>
>
> On Mon, Feb 10, 2014 at 3:04 PM, Matthew Brett wrote:
>
>> Hi,
>>
>> On Mon, Feb 10, 2014 at 7:09 AM, Alan G Isaac
>> wrote:
>> [snip]
>> > Just to forestall the usual "just start them with arrays, eventually
>> they'll
>> > be grateful" reply, I wou
On Mon, Feb 10, 2014 at 3:45 PM, alex wrote:
> On Mon, Feb 10, 2014 at 2:36 PM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Mon, Feb 10, 2014 at 6:26 AM, Nathaniel Smith wrote:
> >> On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
> >>> Hello list,
> >>>
> >>> I wrote this mini-nep for numpy but I've
Hi,
On Mon, Feb 10, 2014 at 12:39 PM, wrote:
>
>
> On Mon, Feb 10, 2014 at 3:04 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Mon, Feb 10, 2014 at 7:09 AM, Alan G Isaac
>> wrote:
>> [snip]
>> > Just to forestall the usual "just start them with arrays, eventually
>> > they'll
>> > be grateful"
Hi,
On Mon, Feb 10, 2014 at 12:44 PM, Charles R Harris
wrote:
>
>
>
> On Mon, Feb 10, 2014 at 1:23 PM, Alan G Isaac wrote:
>>
>> On 2/10/2014 3:04 PM, Matthew Brett wrote:
>> > I teach psychologists and neuroscientists mainly
>>
>>
>> I must suspect that notebook was not for
>> **undergraduate**
On Mon, Feb 10, 2014 at 2:36 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Feb 10, 2014 at 6:26 AM, Nathaniel Smith wrote:
>> On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
>>> Hello list,
>>>
>>> I wrote this mini-nep for numpy but I've been advised it is more
>>> appropriate for discussion on the li
On Mon, Feb 10, 2014 at 1:23 PM, Alan G Isaac wrote:
> On 2/10/2014 3:04 PM, Matthew Brett wrote:
> > I teach psychologists and neuroscientists mainly
>
>
> I must suspect that notebook was not for
> **undergraduate** psychology students.
> At least, not the ones I usually meet.
>
> SymPy is grea
On Mon, Feb 10, 2014 at 3:04 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Feb 10, 2014 at 7:09 AM, Alan G Isaac
> wrote:
> [snip]
> > Just to forestall the usual "just start them with arrays, eventually
> they'll
> > be grateful" reply, I would want to hear that suggestion only from
> someone
> > w
Hi,
On Mon, Feb 10, 2014 at 12:23 PM, Alan G Isaac wrote:
> On 2/10/2014 3:04 PM, Matthew Brett wrote:
>> I teach psychologists and neuroscientists mainly
>
> I must suspect that notebook was not for
> **undergraduate** psychology students.
> At least, not the ones I usually meet.
Well - in this
On 2/10/2014 3:04 PM, Matthew Brett wrote:
> I teach psychologists and neuroscientists mainly
I must suspect that notebook was not for
**undergraduate** psychology students.
At least, not the ones I usually meet.
SymPy is great but for those without background
it is at best awkward. It certainl
Hi,
On Mon, Feb 10, 2014 at 7:09 AM, Alan G Isaac wrote:
[snip]
> Just to forestall the usual "just start them with arrays, eventually they'll
> be grateful" reply, I would want to hear that suggestion only from someone
> who has used it successfully with undergraduates in the social sciences.
I
On Mon, Feb 10, 2014 at 2:49 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Feb 10, 2014 at 11:44 AM, wrote:
> >
> >
> > On Mon, Feb 10, 2014 at 2:12 PM, eat wrote:
> >>
> >>
> >>
> >>
> >> On Mon, Feb 10, 2014 at 9:08 PM, alex wrote:
> >>>
> >>> On Mon, Feb 10, 2014 at 2:03 PM, eat wrote:
> >>>
On Mon, Feb 10, 2014 at 2:49 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Feb 10, 2014 at 11:44 AM, wrote:
> >
> >
> > On Mon, Feb 10, 2014 at 2:12 PM, eat wrote:
> >>
> >>
> >>
> >>
> >> On Mon, Feb 10, 2014 at 9:08 PM, alex wrote:
> >>>
> >>> On Mon, Feb 10, 2014 at 2:03 PM, eat wrote:
> >>>
On Mon, Feb 10, 2014 at 10:09 AM, Alan G Isaac wrote:
> On 2/9/2014 5:55 PM, alex wrote:
> > I'm working on the same kinds of problems in scipy development
> > (functions involving sparse matrices and abstract linear operators)
>
>
> And how is numpy's matrix object getting in your way?
> Your in
Hi,
On Mon, Feb 10, 2014 at 11:44 AM, wrote:
>
>
> On Mon, Feb 10, 2014 at 2:12 PM, eat wrote:
>>
>>
>>
>>
>> On Mon, Feb 10, 2014 at 9:08 PM, alex wrote:
>>>
>>> On Mon, Feb 10, 2014 at 2:03 PM, eat wrote:
>>> > Rhetorical or not, but FWIW I'll prefer to take singular value
>>> > decompositi
On Mon, Feb 10, 2014 at 2:12 PM, eat wrote:
>
>
>
> On Mon, Feb 10, 2014 at 9:08 PM, alex wrote:
>
>> On Mon, Feb 10, 2014 at 2:03 PM, eat wrote:
>> > Rhetorical or not, but FWIW I'll prefer to take singular value
>> decomposition
>> > (u, s, vt= svd(x)) and then based on the singular values s
Hi,
On Mon, Feb 10, 2014 at 6:26 AM, Nathaniel Smith wrote:
> On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
>> Hello list,
>>
>> I wrote this mini-nep for numpy but I've been advised it is more
>> appropriate for discussion on the list.
>>
>> """
>> The ``numpy.matrix`` API provides a low barrier
On Mon, Feb 10, 2014 at 9:08 PM, alex wrote:
> On Mon, Feb 10, 2014 at 2:03 PM, eat wrote:
> > Rhetorical or not, but FWIW I'll prefer to take singular value
> decomposition
> > (u, s, vt= svd(x)) and then based on the singular values s I'll estimate
> a
> > "numerically feasible rank" r. Thus t
On Mon, Feb 10, 2014 at 2:03 PM, eat wrote:
> Rhetorical or not, but FWIW I'll prefer to take singular value decomposition
> (u, s, vt= svd(x)) and then based on the singular values s I'll estimate a
> "numerically feasible rank" r. Thus the diagonal of such hat matrix would be
> (u[:, :r]** 2).su
On Mon, Feb 10, 2014 at 7:00 PM, alex wrote:
> On Mon, Feb 10, 2014 at 11:27 AM, wrote:
> > How do we calculate the diagonal of the hat matrix without using N by N
> > matrices?
>
> Not sure if this was a rhetorical question or what, but this seems to work
> leverages = np.square(scipy.linalg.q
On Mon, Feb 10, 2014 at 12:16 PM, Nathaniel Smith wrote:
> On Mon, Feb 10, 2014 at 12:02 PM, Matthieu Brucher
> wrote:
>> Yes, but these will be scipy.sparse matrices, nothing to do with numpy
>> (dense) matrices.
>
> Unfortunately when scipy.sparse matrices interact with dense ndarrays
> (e.g.,
On Mon, Feb 10, 2014 at 12:02 PM, Matthieu Brucher
wrote:
> Yes, but these will be scipy.sparse matrices, nothing to do with numpy
> (dense) matrices.
Unfortunately when scipy.sparse matrices interact with dense ndarrays
(e.g., sparse matrix * dense vector), then you always get back
np.matrix obj
Yes, but these will be scipy.sparse matrices, nothing to do with numpy
(dense) matrices.
Cheers,
Matthieu
2014-02-10 Dinesh Vadhia :
> Scipy sparse uses matrices - I was under the impression that scipy sparse
> only works with matrices or have things moved on?
>
>
>
> ___
On Mon, Feb 10, 2014 at 11:27 AM, wrote:
> How do we calculate the diagonal of the hat matrix without using N by N
> matrices?
Not sure if this was a rhetorical question or what, but this seems to work
leverages = np.square(scipy.linalg.qr(X, mode='economic')[0]).sum(axis=1)
http://www4.ncsu.edu
Scipy sparse uses matrices - I was under the impression that scipy sparse only
works with matrices or have things moved on?
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Mon, Feb 10, 2014 at 11:16 AM, Alexander Belopolsky wrote:
>
> On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
>>
>> On the other hand, it really needs to be deprecated.
>
>
> While numpy.matrix may have its problems, a NEP should list a better
> rationale than the above to gain acceptance.
>
> Pe
On Mon, Feb 10, 2014 at 10:09 AM, Alan G Isaac wrote:
> On 2/9/2014 5:55 PM, alex wrote:
> > I'm working on the same kinds of problems in scipy development
> > (functions involving sparse matrices and abstract linear operators)
>
>
> And how is numpy's matrix object getting in your way?
> Your in
On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
> On the other hand, it really needs to be deprecated.
While numpy.matrix may have its problems, a NEP should list a better
rationale than the above to gain acceptance.
Personally, I decided not to use numpy.matrix in production code about 10
years a
On 2/9/2014 5:55 PM, alex wrote:
> I'm working on the same kinds of problems in scipy development
> (functions involving sparse matrices and abstract linear operators)
And how is numpy's matrix object getting in your way?
Your initial post simply treated the desirability of
deprecation as a given
On Sun, Feb 9, 2014 at 4:59 PM, alex wrote:
> Hello list,
>
> I wrote this mini-nep for numpy but I've been advised it is more
> appropriate for discussion on the list.
>
> """
> The ``numpy.matrix`` API provides a low barrier to using Python
> for linear algebra, just as the pre-3 Python ``input`
Hi,
On Sun, Feb 9, 2014 at 2:55 PM, alex wrote:
> On Sun, Feb 9, 2014 at 5:12 PM, Alan G Isaac wrote:
>> On 2/9/2014 4:59 PM, alex wrote:
>>> """
>>> The ``numpy.matrix`` API provides a low barrier to using Python
>>> for linear algebra, just as the pre-3 Python ``input`` function
>>> and ``print
On Sun, Feb 9, 2014 at 5:12 PM, Alan G Isaac wrote:
> On 2/9/2014 4:59 PM, alex wrote:
>> """
>> The ``numpy.matrix`` API provides a low barrier to using Python
>> for linear algebra, just as the pre-3 Python ``input`` function
>> and ``print`` statement provided low barriers to using Python for
>>
On 2/9/2014 4:59 PM, alex wrote:
> """
> The ``numpy.matrix`` API provides a low barrier to using Python
> for linear algebra, just as the pre-3 Python ``input`` function
> and ``print`` statement provided low barriers to using Python for
> automatically evaluating input and for printing output.
>
Hello list,
I wrote this mini-nep for numpy but I've been advised it is more
appropriate for discussion on the list.
"""
The ``numpy.matrix`` API provides a low barrier to using Python
for linear algebra, just as the pre-3 Python ``input`` function
and ``print`` statement provided low barriers to
75 matches
Mail list logo
