On Aug 12, 2015 11:12 PM, Jaime Fernández del Río jaime.f...@gmail.com
wrote:
On Wed, Aug 12, 2015 at 2:03 PM, Nathan Goldbaum nathan12...@gmail.com
wrote:
Hi all,
I've been testing the package I spend most of my time on, yt, under
numpy 1.10b1 since the announcement went out.
I think I've
On Wed, Aug 12, 2015 at 2:03 PM, Nathan Goldbaum nathan12...@gmail.com
wrote:
Hi all,
I've been testing the package I spend most of my time on, yt, under numpy
1.10b1 since the announcement went out.
I think I've narrowed down and fixed all of the test failures that cropped
up except for
Hi,
On Wed, Aug 12, 2015 at 12:23 PM, Sebastian Berg
sebast...@sipsolutions.net wrote:
On Mi, 2015-08-12 at 01:07 -0700, Nathaniel Smith wrote:
On Wed, Aug 12, 2015 at 12:51 AM, Sebastian Berg
sebast...@sipsolutions.net wrote:
On Mi, 2015-08-12 at 09:41 +0200, Jens Jørgen Mortensen wrote:
On Thu, Aug 13, 2015 at 12:09 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On Wed, Aug 12, 2015 at 2:03 PM, Nathan Goldbaum nathan12...@gmail.com
wrote:
Hi all,
I've been testing the package I spend most of my time on, yt, under numpy
1.10b1 since the announcement went out.
I
On Thu, Aug 13, 2015 at 9:44 AM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Thu, Aug 13, 2015 at 12:09 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On Wed, Aug 12, 2015 at 2:03 PM, Nathan Goldbaum nathan12...@gmail.com
wrote:
Hi all,
I've been testing the package
On 2015-08-13 08:52:22, Anne Archibald peridot.face...@gmail.com
wrote:
My current approach is to build an empty virtualenv, pip install
nose, and from the numpy root directory do python setup.py
build_ext --inplace and python -c 'import numpy;
numpy.test()'. This works, for my stock
Did you do a git clean -fxd before re-installing?
On Thu, Aug 13, 2015 at 2:34 PM, Sebastian Berg sebast...@sipsolutions.net
wrote:
Hey,
just for hacking/testing, I tried to add to shape.c:
/*NUMPY_API
*
* Checks if memory overlap exists
*/
NPY_NO_EXPORT int
On Thu, Aug 13, 2015 at 10:00 AM, Sebastian Berg sebast...@sipsolutions.net
wrote:
On Do, 2015-08-13 at 15:52 +, Anne Archibald wrote:
Hi,
What is a sensible way to work on (modify, compile, and test) numpy?
There is documentation about contributing to numpy at:
Hey,
just for hacking/testing, I tried to add to shape.c:
/*NUMPY_API
*
* Checks if memory overlap exists
*/
NPY_NO_EXPORT int
PyArray_ArraysShareMemory(PyArrayObject *arr1, PyArrayObject *arr2, int
work) {
return solve_may_share_memory(arr1, arr2, work);
}
and to numpy_api.py:
#
On Do, 2015-08-13 at 14:36 -0400, Benjamin Root wrote:
Did you do a git clean -fxd before re-installing?
Yup.
On Thu, Aug 13, 2015 at 2:34 PM, Sebastian Berg
sebast...@sipsolutions.net wrote:
Hey,
just for hacking/testing, I tried to add to shape.c:
This doesn't answer your question but: why? If you're not distributing a
Python project, there is no reason to use distutils instead of a sane build
system.
Come on. We don't take it seriously, and neither do the Python core devs.
It's also pretty much completely unsupported.
On Thu, Aug 13, 2015 at 7:59 AM, Nathan Goldbaum nathan12...@gmail.com
wrote:
On Thu, Aug 13, 2015 at 9:44 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Thu, Aug 13, 2015 at 12:09 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On Wed, Aug 12, 2015 at 2:03 PM,
On Thu, Aug 13, 2015 at 4:34 PM, Matthew Brett matthew.br...@gmail.com
wrote:
On Thu, Aug 13, 2015 at 1:04 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Wed, Aug 12, 2015 at 12:23 PM, Sebastian Berg
sebast...@sipsolutions.net wrote:
On Mi, 2015-08-12 at 01:07 -0700,
On Thu, Aug 13, 2015 at 1:04 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Wed, Aug 12, 2015 at 12:23 PM, Sebastian Berg
sebast...@sipsolutions.net wrote:
On Mi, 2015-08-12 at 01:07 -0700, Nathaniel Smith wrote:
On Wed, Aug 12, 2015 at 12:51 AM, Sebastian Berg
So as Julian helped me, it was the wrong style of the function, the
curly bracket has to go on the next line for the API generation to pick
it up.
- Sebastian
On Do, 2015-08-13 at 20:42 +0200, Sebastian Berg wrote:
On Do, 2015-08-13 at 14:36 -0400, Benjamin Root wrote:
Did you do a git clean
Hi Casey,
On Wed, Aug 12, 2015 at 11:46 PM, Casey Deen d...@mpia.de wrote:
Hi Pearu-
Thanks so much! This works! Can you point me to a reference for the
format of the .pyf files? My ~day of searching found a few pages on the
scipy website, but nothing which went into this amount of
On Thu, Aug 13, 2015 at 8:45 PM, Christian Engwer
christian.eng...@uni-muenster.de wrote:
This doesn't answer your question but: why? If you're not
distributing a
Python project, there is no reason to use distutils instead of a sane
build
system.
Come on. We don't take it
On Thu, Aug 13, 2015 at 9:57 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On Thu, Aug 13, 2015 at 7:59 AM, Nathan Goldbaum nathan12...@gmail.com
wrote:
On Thu, Aug 13, 2015 at 9:44 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Thu, Aug 13, 2015 at 12:09 AM,
Hi,
I am new to NumPy, Can someone help me in understanding below code.
names = np.array(['Bob', 'Joe', 'Will', 'Bob', 'Will', 'Joe', 'Joe'])
data = np.random.random((7,4))
print data
[[ 0.85402649 0.12827655 0.580 0.86288236]
[ 0.30162683 0.45269508 0.98098039 0.1291469 ]
[
Hi,
What is a sensible way to work on (modify, compile, and test) numpy?
There is documentation about contributing to numpy at:
http://docs.scipy.org/doc/numpy-dev/dev/index.html
and:
http://docs.scipy.org/doc/numpy-dev/dev/gitwash/development_workflow.html
but these are entirely focused on
On Do, 2015-08-13 at 15:52 +, Anne Archibald wrote:
Hi,
What is a sensible way to work on (modify, compile, and test) numpy?
There is documentation about contributing to numpy at:
http://docs.scipy.org/doc/numpy-dev/dev/index.html
and:
21 matches
Mail list logo
