On Sa, 2014-07-05 at 22:13 -0400, Benjamin Root wrote:
Drats... I actually know those two topics... and I might have free
time tomorrow afternoon at SciPy. Maybe I could take a peek at it?
Maybe if you have time. It is just the attempt_1d_fallback function in
the pull request
There is no os.mkfifo on Windows.
Sturla
Valentin Haenel valen...@haenel.co wrote:
sorry, for the top-post, but should we add this as an issue on the
github tracker? I'd like to revisit it this summer.
V-
* Julian Taylor jtaylor.deb...@googlemail.com [2014-04-18]:
On 18.04.2014 18:29,
Sebastian Berg sebast...@sipsolutions.net wrote:
Could it be useful for structured arrays?
Not sure how. The named columns seem like a decent point to me.
NumPy is naming the fields, not the axes, so it might be more useful for
Pandas than NumPy. For example if we have an image with r,g,b
On Sun, Jul 6, 2014 at 2:24 AM, Julian Taylor jtaylor.deb...@googlemail.com
wrote:
On 05.07.2014 19:11, David Cournapeau wrote:
On Sun, Jul 6, 2014 at 1:55 AM, Julian Taylor
jtaylor.deb...@googlemail.com mailto:jtaylor.deb...@googlemail.com
wrote:
On 05.07.2014 18:40, David
I see that a solution has already been found and merged. Are there any
remaining issues for matplotlib to resolve?
On Sun, Jul 6, 2014 at 2:30 AM, Sebastian Berg sebast...@sipsolutions.net
wrote:
On Sa, 2014-07-05 at 22:13 -0400, Benjamin Root wrote:
Drats... I actually know those two
On Sun, Jul 6, 2014 at 11:54 AM, Benjamin Root ben.r...@ou.edu wrote:
I see that a solution has already been found and merged. Are there any
remaining issues for matplotlib to resolve?
You might take a look at the fixes in the matplotlib PR. They struck me as
a bit hasty rather than fixes for
When did Cython become a build requirement? I remember discussing the use
of Cython a while back, and IIRC the agreement was that both the cython
code and the generated C files would be included in version control so that
cython wouldn't be a build requirement, only a developer requirement when
On So, 2014-07-06 at 12:07 -0600, Charles R Harris wrote:
On Sun, Jul 6, 2014 at 11:54 AM, Benjamin Root ben.r...@ou.edu
wrote:
I see that a solution has already been found and merged. Are
there any remaining issues for matplotlib to resolve?
On 6 July 2014 20:40, Benjamin Root ben.r...@ou.edu wrote:
When did Cython become a build requirement? I remember discussing the use
of Cython a while back, and IIRC the agreement was that both the cython
code and the generated C files would be included in version control so that
cython
On Sun, Jul 6, 2014 at 7:40 PM, Benjamin Root ben.r...@ou.edu wrote:
When did Cython become a build requirement? I remember discussing the use of
Cython a while back, and IIRC the agreement was that both the cython code
and the generated C files would be included in version control so that
While trying to wrap my head around the issues with matplotlib's tri module
and the new numpy indexing, I have made some test cases where I wonder if
warnings should be issued.
import numpy as np
a = np.ones((10,))
all_false = np.zeros((10,), dtype=bool)
a[all_false] = np.array([2.0]) # the
Ok, must have missed that discussion. I don't like the reasoning, but that
boat has sailed.
On Sun, Jul 6, 2014 at 3:00 PM, Robert Kern robert.k...@gmail.com wrote:
On Sun, Jul 6, 2014 at 7:40 PM, Benjamin Root ben.r...@ou.edu wrote:
When did Cython become a build requirement? I remember
On So, 2014-07-06 at 15:32 -0400, Benjamin Root wrote:
While trying to wrap my head around the issues with matplotlib's tri
module and the new numpy indexing, I have made some test cases where I
wonder if warnings should be issued.
import numpy as np
a = np.ones((10,))
all_false =
On Sun, Jul 6, 2014 at 1:32 PM, Benjamin Root ben.r...@ou.edu wrote:
While trying to wrap my head around the issues with matplotlib's tri
module and the new numpy indexing, I have made some test cases where I
wonder if warnings should be issued.
import numpy as np
a = np.ones((10,))
re: deprecation warnings... that's what I get when I am working on my
non-dev box because I am at the conference, and have gotten too used to the
setup of my dev box...
as for the broadcasting issue, I can see it for the second case, but the
first case still doesn't sit right with me. My
The idea is that there be a short-hand for creating arrays as there is for
matrices:
np.mat('.2 .7 .1; .3 .5 .2; .1 .1 .9')
It was suggested in GitHub issue #4817
https://github.com/numpy/numpy/issues/4817 in light that it would be
beneficial to beginners and to presenters during
On So, 2014-07-06 at 16:14 -0400, Benjamin Root wrote:
re: deprecation warnings... that's what I get when I am working on my
non-dev box because I am at the conference, and have gotten too used
to the setup of my dev box...
as for the broadcasting issue, I can see it for the second case,
On Sun, Jul 6, 2014 at 9:35 PM, Daniel da Silva
var.mail.dan...@gmail.com wrote:
The idea is that there be a short-hand for creating arrays as there is for
matrices:
np.mat('.2 .7 .1; .3 .5 .2; .1 .1 .9')
It was suggested in GitHub issue #4817 in light that it would be beneficial
to
On Sun, Jul 6, 2014 at 9:14 PM, Benjamin Root ben.r...@ou.edu wrote:
as for the broadcasting issue, I can see it for the second case, but the
first case still doesn't sit right with me. My understanding of broadcasting
is to effectively *expand* an array to match the shape of another array (or
I guess I always treated scalars as something special when it comes to
broadcasting. Seeing these examples, I can see how my grokking of
broadcasting was incomplete.
I still think that the assignment of an array of values (as opposed to a
scalar) to nothing could potentially mask deeper issues,
On 2014/07/06, 11:43 AM, Nathaniel Smith wrote:
On Sun, Jul 6, 2014 at 9:35 PM, Daniel da Silva
var.mail.dan...@gmail.com wrote:
The idea is that there be a short-hand for creating arrays as there is for
matrices:
np.mat('.2 .7 .1; .3 .5 .2; .1 .1 .9')
It was suggested in GitHub issue
Thanks!
On Fri, Jul 4, 2014 at 1:53 AM, Robert Kern robert.k...@gmail.com wrote:
On Thu, Jul 3, 2014 at 10:53 PM, Ted Sandler ted.sand...@gmail.com
wrote:
Thanks. No, it's not what I'm looking for.
I'm looking for the code that parses the string i8 in the npy file
array
header's
On Sun, Jul 6, 2014 at 6:06 PM, Eric Firing efir...@hawaii.edu wrote:
(I'm not entirely convinced
np.arr() is a good idea at all; but if it is, it must be kept simple.)
If you are going to introduce this functionality, please don't call it
np.arr.
Right now, np.atab presents you with a
On 2014/07/06, 4:27 PM, Alexander Belopolsky wrote:
On Sun, Jul 6, 2014 at 6:06 PM, Eric Firing efir...@hawaii.edu
mailto:efir...@hawaii.edu wrote:
(I'm not entirely convinced
np.arr() is a good idea at all; but if it is, it must be kept simple.)
If you are going to introduce
On Sun, Jul 6, 2014 at 10:59 PM, Eric Firing efir...@hawaii.edu wrote:
I would suggest calling it something like np.array_simple or
np.array_from_string, but the best choice IMO, would be
np.ndarray.from_string (a static constructor method).
I think the problem is that this defeats the
Just so. The fixes for 1.9.0b1 are now in that branch ready for the next
beta.
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
26 matches
Mail list logo
