names == 'Bob' returns a boolean array [True, False, False, True, False,
False, False], and data[boolean_array] returns all those elements of data
where the boolean array is True. data is a list of 7 lists, so the two
lists corresponding to True values are returned.
Read the Numpy basics and
For what it's worth, also from my astropy perspective I think hat any index
array should be a base ndarray!
-- Marten
On Fri, Aug 14, 2015 at 7:11 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On Thu, Aug 13, 2015 at 9:57 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On
On Aug 14, 2015 09:16, Chris Barker chris.bar...@noaa.gov wrote:
On Thu, Aug 13, 2015 at 11:25 AM, Stefan van der Walt
stef...@berkeley.edu wrote:
(for
example python setup.py develop, although suggested by
setup.py itself, claims that develop is not a command).
develop is a command
On Fri, Aug 14, 2015 at 10:08 AM, Benjamin Root ben.r...@ou.edu wrote:
I used to be a huge advocate for the develop mode, but not anymore. I
have run into way too many Heisenbugs that would clear up if I nuked my
source tree and re-clone.
well, you do need to remember to clean out once in a
On 08/13/2015 11:52 AM, 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:
On 08/14/2015 01:52 PM, Pauli Virtanen wrote:
14.08.2015, 20:45, Allan Haldane kirjoitti:
[clip]
Related to this, does anyone know how to debug numpy in gdb with proper
symbols/source lines, like I can do with other C extensions? I've tried
modifying numpy distutils to try to add the right
On Thu, Aug 13, 2015 at 11:25 AM, Stefan van der Walt stef...@berkeley.edu
wrote:
(for
example python setup.py develop, although suggested by
setup.py itself, claims that develop is not a command).
develop is a command provided by setuptools, not distutils itself.
I find it absolutely
14.08.2015, 20:45, Allan Haldane kirjoitti:
[clip]
Related to this, does anyone know how to debug numpy in gdb with proper
symbols/source lines, like I can do with other C extensions? I've tried
modifying numpy distutils to try to add the right compiler/linker flags,
without success.
I used to be a huge advocate for the develop mode, but not anymore. I
have run into way too many Heisenbugs that would clear up if I nuked my
source tree and re-clone.
I should also note that there is currently an open issue with pip install
-e and namespace packages. This has been reported to
On 2015-08-14 10:08:11, Benjamin Root ben.r...@ou.edu wrote:
I should also note that there is currently an open issue with
pip install -e and namespace packages. This has been reported
to matplotlib with regards to mpl_toolkits. Essentially, if you
have namespace packages, it doesn't get
15.08.2015, 01:44, Chris Barker kirjoitti:
[clip]
numpy doesn't use namespace packages, so develop mode works there.
The develop mode is mainly useful with a virtualenv.
Otherwise, you install work-in-progress development version into your
~/.local which then breaks everything else. In addition
I think it's clear that develop/-e does not work well together with
namespace packages. As noted on the relevant matplotlib issue
https://github.com/matplotlib/matplotlib/issues/4907 I think the issue with
namespace packages is essentially this well known one
https://github.com/pypa/pip/issues/3
Dear Ralf,
I stared at it for a while, and can't figure it out despite you following
the example in the add_npy_pkg_config docstring pretty much to the letter.
When you see that the error is generated in a function that starts with ``#
XXX: another ugly workaround to circumvent distutils
13 matches
Mail list logo
