Re: [Numpy-discussion] py2/py3 pickling

24, 2015, at 2:30 PM, Nathaniel Smith n...@pobox.com wrote: On Aug 24, 2015 9:29 AM, Pauli Virtanen p...@iki.fi mailto:p...@iki.fi wrote: 24.08.2015, 01:02, Chris Laumann kirjoitti: [clip] Is there documentation about the limits and workarounds for py2/py3 pickle/np.save/load

[Numpy-discussion] py2/py3 pickling

Hi all- Is there documentation about the limits and workarounds for py2/py3 pickle/np.save/load compatibility? I haven't found anything except developer bug tracking discussions (eg. #4879 in github numpy). The kinds of errors you get can be really obscure when save/loading complicated

Re: [Numpy-discussion] It looks like Py 3.5 will include a dedicated infix matrix multiply operator

indistinguishable types for 2d arrays with slightly different semantics for a small subset of operations is terrible. Best, C --  Chris Laumann Sent with Airmail On March 14, 2014 at 7:16:24 PM, Christophe Bal (projet...@gmail.com) wrote: This id good for Numpyists but this will be another operator

Re: [Numpy-discussion] [help needed] associativity and precedence of '@'

is more complicated than can be expressed as left-right or right-left (because some matrices might be diagonal, CSR or CSC), which is why the preference is only weak. I don’t see a down-side in the use-case that it is actually associative (as in matrix-matrix-vector).  Best, Chris --  Chris Laumann

Re: [Numpy-discussion] Memory leak?

builds only two sentences into the paragraph. Best, Chris --  Chris Laumann Sent with Airmail On January 31, 2014 at 9:31:40 AM, Julian Taylor (jtaylor.deb...@googlemail.com) wrote: On 31.01.2014 18:12, Nathaniel Smith wrote: On Fri, Jan 31, 2014 at 4:29 PM, Benjamin Root ben.r

Re: [Numpy-discussion] Memory leak?

return due to the PyObject_Malloc usage in git master, but it doesn't affect 1.8.0 On Fri, Jan 31, 2014 at 7:20 AM, Chris Laumann chris.laum...@gmail.com wrote: Hi all- The following snippet appears to leak memory badly (about 10 MB per execution): P = randint(0,2,(30,13)) for i in range(50): print

[Numpy-discussion] Memory leak?

in range(50):     print \r, i, /, 50     for ai in ndindex((2,)*13):         j = P.dot(ai) There is no leak.  Any thoughts? I’m stumped. Best, Chris --  Chris Laumann Sent with Airmail___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http

[Numpy-discussion] Memory leak in numpy?

Superpack (numpy 1.9) right now but I somehow doubt this behavior will change. Any thoughts? Best, Chris --  Chris Laumann Sent with Airmail___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy

Re: [Numpy-discussion] Bitwise operations and unsigned types

Good morning all-- didn't realize this would generate quite such a buzz. To answer a direct question, I'm using the github master. A few thoughts (from a fairly heavy numpy user for numerical simulations and analysis): The current behavior is confusing and (as far as i can tell) undocumented.

[Numpy-discussion] Bitwise operations and unsigned types

-- Chris Laumann Sent with Sparrow (http://www.sparrowmailapp.com/?sig) ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion