On Mar 3, 2014 3:16 AM, Charles R Harris charlesr.har...@gmail.com
wrote:
This is from OS X 9
if ((err = SSLHashSHA1.update(hashCtx, serverRandom)) != 0)
goto fail;
if ((err = SSLHashSHA1.update(hashCtx, signedParams)) != 0)
goto fail;
goto fail;
if
Would something like:
#include numpy/arrayobject.h
// for compatibility with Numpy version = 1.6
#if NPY_FEATURE_VERSION 0x0007
#define NPY_ARRAY_FARRAY NPY_FARRAY
// other defines for deprecated stuff
// ...
#endif
Be robust enough ?
2014-02-28 14:31 GMT+00:00 Ghislain Vaillant
Todd toddr...@gmail.com Wrote in message:
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
use modern programming languages with well designed exception handling
--
And, you know... unit tests to actually know if a the code would reject a
spoofed certificate?
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Hi Sze
You need Python 2.7.x 32-bit version installed.
I experienced this once when I accidentally had the 64-bit version of
Python installed.
kind regards
Søren
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
Hi All,
Julian Taylor has put windows binaries and sources for the 1.8.1 release
candidate up on
sourceforgehttp://sourceforge.net/projects/numpy/files/NumPy/1.8.1rc1/.
If things go well, it will taken to a full release in a week or so.
Chuck
___
And significant indentation!
really, no one beat me to that?
;-)
There was a nice Blog post about this from a Google Chrome developer --
less critical than I'd think, who pointed out that it's really hard to
write unit tests for this sort of thing, due to the need for a LOT
of scaffolding --
On Sat, Mar 1, 2014 at 6:09 PM, Alexander Belopolsky ndar...@mac.comwrote:
On Fri, Feb 28, 2014 at 10:34 AM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
Whatever happened to duck typing?
http://legacy.python.org/dev/peps/pep-3119/#abcs-vs-duck-typing
Sure -- but I'm afraid
On Sat, Mar 1, 2014 at 6:42 AM, faisal anees
mohammedfaisal.an...@students.iiit.ac.in wrote:
I am Mohammed Faisal Anees , a Computer Science student at IIIT-
Hyderabad. I was going though the ideas page and I found Improve Numpy
datetime functionality really interesting ,
It's great to have
On Mar 3, 2014, at 11:59 AM, Chris Barker chris.bar...@noaa.gov wrote:
And significant indentation!
really, no one beat me to that?
;-)
There was a nice Blog post about this from a Google Chrome developer -- less
critical than I'd think, who pointed out that it's really hard to write
On Mo, 2014-03-03 at 09:23 -0700, Charles R Harris wrote:
Hi All,
Julian Taylor has put windows binaries and sources for the 1.8.1
release candidate up on sourceforge. If things go well, it will taken
to a full release in a week or so.
Thanks to both of you. Also for sieving through all
On Mon, Mar 3, 2014 at 6:38 PM, Chris Barker chris.bar...@noaa.gov wrote:
On Sat, Mar 1, 2014 at 6:42 AM, faisal anees
mohammedfaisal.an...@students.iiit.ac.in wrote:
I am Mohammed Faisal Anees , a Computer Science student at IIIT-
Hyderabad. I was going though the ideas page and I found
hi,
as the numpy gsoc topic page is a little short on options I was thinking
about adding two topics for interested students. But as I have no
experience with gsoc or mentoring and the ideas are not very fleshed out
yet I'd like to ask if it might make sense at all:
1. configurable algorithm
Hi all,
I'm using numpy 1.8.0 (osx 10.9, python 2.7.6) and I can't understand dtype
promotion in the following case:
Z = np.zeros((2,2),dtype=np.float32) + 1
print Z.dtype
float32
Z = np.zeros((2,2),dtype=np.float32) + (1,1)
print Z.dtype
float64
Is this the expected behavior ?
What it
On Mon, 2014-03-03 at 22:06 +0100, Nicolas Rougier wrote:
Hi all,
I'm using numpy 1.8.0 (osx 10.9, python 2.7.6) and I can't understand dtype
promotion in the following case:
Z = np.zeros((2,2),dtype=np.float32) + 1
print Z.dtype
float32
Z = np.zeros((2,2),dtype=np.float32) +
The tuple gets cast to an ndarray; which invokes a different codepath than
the scalar addition.
Somehow, numpy has gotten more aggressive at upcasting to float64 as of
1.8, but I havnt been able to discover the logic behind it either.
On Mon, Mar 3, 2014 at 10:06 PM, Nicolas Rougier
On Sun, Mar 2, 2014 at 5:12 AM, Leo Mao lmao20...@gmail.com wrote:
Hello Ray,
Thanks for your suggestion! I just read the links you provided and I think
I can implement it as long as I do further research on zoom fft algorithm.
So I wonder if this can be a GSoC project?
By itself that's not
On Mon, 2014-03-03 at 22:26 +0100, Eelco Hoogendoorn wrote:
The tuple gets cast to an ndarray; which invokes a different codepath
than the scalar addition.
Somehow, numpy has gotten more aggressive at upcasting to float64 as
of 1.8, but I havnt been able to discover the logic behind it
On Mon, Mar 3, 2014 at 8:20 PM, Julian Taylor jtaylor.deb...@googlemail.com
wrote:
hi,
as the numpy gsoc topic page is a little short on options I was thinking
about adding two topics for interested students. But as I have no
experience with gsoc or mentoring and the ideas are not very
IIRC, this is dependent on whether you are using 32bit versus 64bit numpy.
All regular integer numbers can fit in 32 bits (is that right?), but the
1.1 is treated as a float32 if on a 32 bit NumPy or as float64 if on a 64
bit NumPy.
That's my stab at it.
Ben Root
On Mon, Mar 3, 2014 at 4:06
I never noticed this kind of cast before (1.8.0), it's just a bit surprising.
It was convenient to write translations (for a bunch of points) such as:
Z = np.ones((n,2),dtype=np.float32) + (300,300)
but I can live with Z += 300,300
Nicolas
On 03 Mar 2014, at 23:02, Benjamin Root
Oops, I just now noticed that it was (1,1) and not (1.1). I really need to
set a better font that makes the period and the comma more different...
Ben Root
On Mon, Mar 3, 2014 at 5:12 PM, Nicolas Rougier nicolas.roug...@inria.frwrote:
I never noticed this kind of cast before (1.8.0), it's
On Mon, 2014-03-03 at 23:12 +0100, Nicolas Rougier wrote:
I never noticed this kind of cast before (1.8.0), it's just a bit surprising.
It was convenient to write translations (for a bunch of points) such as:
Z = np.ones((n,2),dtype=np.float32) + (300,300)
but I can live with Z +=
23 matches
Mail list logo
