On Wed, Apr 8, 2015 at 10:20 PM, Robert Kern robert.k...@gmail.com wrote:
On Wed, Apr 8, 2015 at 8:40 PM, Ralf Gommers ralf.gomm...@gmail.com
wrote:
To address in detail the list of Matthew you mention above:
* implement orthogonal indexing as a method arr.sensible_index[...]
That's
On Wed, Apr 8, 2015 at 2:09 PM, Alan G Isaac alan.is...@gmail.com wrote:
That analogy fails because it suggests a private conversation. This list is
extremely public.
For example, I am just a user, and I am on it. I can tell you that as a
long-time numpy user
my reaction to the proposal to
On Apr 5, 2015 7:04 AM, Robert Kern robert.k...@gmail.com wrote:
On Sat, Apr 4, 2015 at 10:38 PM, Nathaniel Smith n...@pobox.com wrote:
On Apr 4, 2015 4:12 AM, Todd toddr...@gmail.com wrote:
There was no break as large as this. In fact I would say this is even
a larger change than any
I think the rationale is to allow selection of whole rows / columns. If you
want to choose a single element from each row/column, then, yes, you have to
pass np.arange(...). There is also np.choose function, but not recommended to
use for such cases as far as I understand. I'm not an expert,
On Wed, Apr 8, 2015 at 2:06 AM, Nathaniel Smith n...@pobox.com wrote:
On Apr 5, 2015 7:04 AM, Robert Kern robert.k...@gmail.com wrote:
On Sat, Apr 4, 2015 at 10:38 PM, Nathaniel Smith n...@pobox.com wrote:
On Apr 4, 2015 4:12 AM, Todd toddr...@gmail.com wrote:
There was no
Research position in the Brazilian Research Institute for Science and
Neurotechnology – BRAINN
Postdoc researcher to work with software development for medical imaging
The Brazilian Research Institute for Neuroscience and Neurotechnology
(BRAINN) (www.brainn.org.br) focuses on the investigation
On Wed, Apr 8, 2015 at 1:38 PM, Robert Kern robert.k...@gmail.com wrote:
On Wed, Apr 8, 2015 at 2:06 AM, Nathaniel Smith n...@pobox.com wrote:
On Apr 5, 2015 7:04 AM, Robert Kern robert.k...@gmail.com wrote:
On Sat, Apr 4, 2015 at 10:38 PM, Nathaniel Smith n...@pobox.com wrote:
On Apr
On Apr 8, 2015 2:16 PM, Andreas Hilboll li...@hilboll.de wrote:
Hi all,
I'm commonly using function signatures like
def myfunc(a, b, c=None):
if c is None:
# do something ...
...
where c is an optional array argument. For some time now, I'm getting a
On Mon, Apr 6, 2015 at 4:49 PM, Nicholas Devenish misno...@gmail.com wrote:
With the indexing example from the documentation:
y = np.arange(35).reshape(5,7)
Why does selecting an item from explicitly every row work as I’d expect:
y[np.array([0,1,2,3,4]),np.array([0,0,0,0,0])]
array([ 0, 7,
On 08.04.2015 20:30, Nathaniel Smith wrote:
On Apr 8, 2015 2:16 PM, Andreas Hilboll li...@hilboll.de
mailto:li...@hilboll.de wrote:
Hi all,
I'm commonly using function signatures like
def myfunc(a, b, c=None):
if c is None:
# do something ...
...
where c is
Spyder supports C.
Thanks for correcting this. I wasn't aware of it.
How was your experience with it?
Best,
-m
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On 2015/04/08 8:09 AM, Alan G Isaac wrote:
That analogy fails because it suggests a private conversation. This list is
extremely public.
For example, I am just a user, and I am on it. I can tell you that as a
long-time numpy user
my reaction to the proposal to change indexing semantics was
I like your idea Josef, I'll add it to the PR. Just to be clear, we should
have something like:
Have a single check_valid keyword arg, which will default to warn, since
that is the current behavior. It will check approximate symmetry, PSDness,
and for NaN infs. Other options on the check_valid
That analogy fails because it suggests a private conversation. This list is
extremely public.
For example, I am just a user, and I am on it. I can tell you that as a
long-time numpy user
my reaction to the proposal to change indexing semantics was (i) OMG YMBFKM and
then
(ii) take a breath;
Hi all,
I'm commonly using function signatures like
def myfunc(a, b, c=None):
if c is None:
# do something ...
...
where c is an optional array argument. For some time now, I'm getting a
FutureWarning: comparison to `None` will result in an elementwise
object
I think spyder supports code highlighting in C and that's all...
There's no way to compile in Spyder, is there?
Shawn
On Tue, Apr 7, 2015 at 2:46 AM, Suzen, Mehmet msu...@gmail.com wrote:
Spyder supports C.
Thanks for correcting this. I wasn't aware of it.
How was your experience with it?
On Wed, Apr 8, 2015 at 9:05 PM, Eric Firing efir...@hawaii.edu wrote:
On 2015/04/08 8:09 AM, Alan G Isaac wrote:
That analogy fails because it suggests a private conversation. This list
is extremely public.
For example, I am just a user, and I am on it. I can tell you that as a
long-time
On Wed, Apr 8, 2015 at 8:05 PM, Eric Firing efir...@hawaii.edu wrote:
Now, can we please get back to consideration of reasonable options?
Sure, but I recommend going back to the actually topical thread (or a new
one), as this one is meta.
--
Robert Kern
On 2015/04/08 9:40 AM, Ralf Gommers wrote:
Their proposal is not being discussed; instead that potentially useful
discussion is being completely derailed by insisting on wanting to talk
about changes to numpy's indexing behavior.
Good point. That was an unintended consequence of my message.
1. I use numpy in teaching.
I have never heard a complaint about its indexing behavior.
Have you heard such complaints?
2. One reason I use numpy in teaching is its indexing behavior.
What specific language provides a better indexing model,
in your opinion?
3. I admit, my students are NOT using
On 2015/04/08 10:02 AM, Alan G Isaac wrote:
3. I admit, my students are NOT using non-boolen fancy indexing on
multidimensional arrays. (As far as I know.) Are yours?
Yes, one attempted to, essentially by accident. That was in my original
message. Please refer back to that. The earlier
Trying to bring the meta back into this thread (sorry for Robert's PB :)...
The only thing I'd like to add, is that it's perhaps worth messaging that:
a PR is just (as the Github folks like to say) a conversation based on
code. It is NOT necessarily something intended explicitly for merging.
In
On Wed, Apr 8, 2015 at 8:40 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
To address in detail the list of Matthew you mention above:
* implement orthogonal indexing as a method arr.sensible_index[...]
That's basically Jaime's PR.
* implement the current non-boolean fancy indexing
On Di, 2015-04-07 at 00:49 +0100, Nicholas Devenish wrote:
With the indexing example from the documentation:
y = np.arange(35).reshape(5,7)
Why does selecting an item from explicitly every row work as I’d expect:
y[np.array([0,1,2,3,4]),np.array([0,0,0,0,0])]
array([ 0, 7, 14, 21, 28])
24 matches
Mail list logo
