Valentin Haenel, Bloscpack definitely looks interesting but I need to take
a careful look first. I will let you know if I like it. Thanks for the
suggestion!
I think you and Nathaniel Smith misunderstood my questions (my fault, since
I did not explain myself well!).
First, Numpy's savez will not d
Besides, the result of numpy.vectorize don't have 'nin' and 'nout' members.
Cheers,
On Wed, Apr 16, 2014 at 2:55 AM, Nathaniel Smith wrote:
> I don't think the names exist currently except as mnemonics in the
> docstring. Patches to improve 'inspect' support would be welcome of
> course.
>
> -n
crc32 extremely fast, and I think zip might use adler32 instead which is
even faster. OTOH compression is incredibly slow, unless you're using one
of the 'just a little bit of compression' formats like blosc or lzo1. If
your npz files are compressed then this is certainly the culprit.
The zip form
On Wed, Apr 16, 2014 at 3:50 PM, Fernando Perez wrote:
> Does argument clinic work with python2 or is it python3 only?
>
> http://legacy.python.org/dev/peps/pep-0436/
>
> It is python3 only, but is should not be hard to adapt it to generate 2/3
compatible code.
Hi Gilberto,
* onefire [2014-04-16]:
> I have been playing with the idea of using Numpy's binary format as a
> lightweight alternative to HDF5 (which I believe is the "right" way to do
> if one does not have a problem with the dependency).
>
> I am pretty happy with the npy format, but the npz
Did you rebuild numpy after rebuilding python? Note that if that works,
then you will likely need to recompile the entire scipy stack (matplotlib,
scipy, etc.).
Ben Root
On Wed, Apr 16, 2014 at 3:23 PM, jaylene wrote:
> Hi,
>
> I rebuilt the python with -enabled_shared to resolve the following
Does argument clinic work with python2 or is it python3 only?
http://legacy.python.org/dev/peps/pep-0436/
f
On Tue, Apr 15, 2014 at 11:55 PM, Nathaniel Smith wrote:
> I don't think the names exist currently except as mnemonics in the
> docstring. Patches to improve 'inspect' support would be
Hi,
I rebuilt the python with -enabled_shared to resolve the following error:
/usr/bin/ld: /usr/local/lib/libpython2.7.a(cobject.o): relocation
R_X86_64_32S against `PyCObject_Type' can not be used when making a
shared object; recompile with -fPIC
/usr/local/lib/libpython2.7.a: could not read sym
Hi all,
I have been playing with the idea of using Numpy's binary format as a
lightweight alternative to HDF5 (which I believe is the "right" way to do
if one does not have a problem with the dependency).
I am pretty happy with the npy format, but the npz format seems to be
broken as far as perfo
For some reason the Python issue 21223 didn't show any activity until I
logged in to post my patch. At which point I saw that haypo had already
submitted pretty much exactly the same patch. *sigh* That was pretty much a
waste of time then. :-|
___
NumPy-D
On 15 April 2014 10:48, Nathaniel Smith wrote:
> Anyone interested in picking this up?
> http://bugs.python.org/issue21233
>
Yes, I'll give it a go.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/n
11 matches
Mail list logo
