On Thu, Apr 25, 2013 at 08:10:32PM +0100, Robert Kern wrote:
> In my opinion, duplicating functionality under different aliases just
> so people can supposedly find things without reading the documentation
> is not a viable strategy for building out an API.
+1. It's been my experience over and ove
Hi,
On Fri, Apr 26, 2013 at 10:02 AM, Andrew Giessel
wrote:
> I like this, thank you Phil.
>
> From what I can see, the ordering of the returned slices when you use more
> than one axis (ie: slices(a, [1,2]), increments the last axis fastest. Does
> this makes sense based on the default ordering
I like this, thank you Phil.
>From what I can see, the ordering of the returned slices when you use more
than one axis (ie: slices(a, [1,2]), increments the last axis fastest.
Does this makes sense based on the default ordering of, say, nditer()? I
know that C-order (row major) and Fortran order
Thank you!
On Fri, Apr 26, 2013 at 12:06 PM, Ognen Duzlevski wrote:
> Should be fixed now.
> Ognen
>
>
> On Fri, Apr 26, 2013 at 10:51 AM, Robert Kern wrote:
>
>> On Fri, Apr 26, 2013 at 4:44 PM, Andreas Hilboll
>> wrote:
>> Unfortunately, Github can only deal with one CNAME, www.numpy.org
Should be fixed now.
Ognen
On Fri, Apr 26, 2013 at 10:51 AM, Robert Kern wrote:
> On Fri, Apr 26, 2013 at 4:44 PM, Andreas Hilboll wrote:
> Unfortunately, Github can only deal with one CNAME, www.numpy.org.
> The
> documentation recommends that one "redirect" the other domains, but
>
On Fri, Apr 26, 2013 at 4:44 PM, Andreas Hilboll wrote:
Unfortunately, Github can only deal with one CNAME, www.numpy.org. The
documentation recommends that one "redirect" the other domains, but
it's not clear exactly what it is referring to. Having an HTTP server
with an A rec
>>> Unfortunately, Github can only deal with one CNAME, www.numpy.org. The
>>> documentation recommends that one "redirect" the other domains, but
>>> it's not clear exactly what it is referring to. Having an HTTP server
>>> with an A record for numpy.scipy.org that just issues HTTP 301
>>> redirec
On Fri, Apr 26, 2013 at 4:30 PM, Andreas Hilboll wrote:
>> Unfortunately, Github can only deal with one CNAME, www.numpy.org. The
>> documentation recommends that one "redirect" the other domains, but
>> it's not clear exactly what it is referring to. Having an HTTP server
>> with an A record for
> Unfortunately, Github can only deal with one CNAME, www.numpy.org. The
> documentation recommends that one "redirect" the other domains, but
> it's not clear exactly what it is referring to. Having an HTTP server
> with an A record for numpy.scipy.org that just issues HTTP 301
> redirects for eve
On Fri, Apr 26, 2013 at 4:11 PM, Robert Kern wrote:
> On Fri, Apr 26, 2013 at 3:20 PM, Christopher Hanley wrote:
>> Dear Numpy Webmasters,
>>
>> Would it be possible to either redirect numpy.scipy.org to www.numpy.org or
>> to the main numpy github landing page? Currently numpy.scipy.org hits a
On Fri, Apr 26, 2013 at 3:20 PM, Christopher Hanley wrote:
> Dear Numpy Webmasters,
>
> Would it be possible to either redirect numpy.scipy.org to www.numpy.org or
> to the main numpy github landing page? Currently numpy.scipy.org hits a
> Github 404 page. As the numpy.scipy.org site still shows
Sorry, I didn't saw the release candidate. I was away for 1 mounts and
didn't read all my email in order.
Normally I try to test the release candidate, but I wasn't able this time.
I have nothing to report again NumPy 1.7.1. I reread the previous emails
and I remark that I badly read the first tim
Dear Numpy Webmasters,
Would it be possible to either redirect numpy.scipy.org to www.numpy.org or
to the main numpy github landing page? Currently numpy.scipy.org hits a
Github 404 page. As the numpy.scipy.org site still shows up in searches it
would be useful to have that address resolve to so
I didn't find the rollaxis solution particularly obvious and also had to
think about what rollaxis did before understanding its usefulness for
iteration.
Now that I've understood it, I'm +1 for the statement that, as it stands,
the proposed iteraxis method doesn't add enough to warrant its inclusio
the "new" documentation
http://stackoverflow.com/questions/1589706/iterating-over-arbitrary-dimension-of-numpy-array
second answer, 1st answer is what I usually use
search term "[numpy] iterate over axis"
Josef
On Fri, Apr 26, 2013 at 9:37 AM, Jason Grout
wrote:
> On 4/26/13 6:33 AM, Robert K
On 4/26/13 6:33 AM, Robert Kern wrote:
> In any case, whether you put the documentation in the rollaxis()
> docstring or in one of the indexing/iteration sections, or
> (preferably) both, I strongly encourage you to do that first and see
> how it goes before adding a new alias.
+1 (for what it's w
On Fri, Apr 26, 2013 at 12:26 PM, Andrew Giessel
wrote:
> I agree with Charles that rollaxis() isn't immediately intuitive.
>
> It seems to me that documentation like this doesn't belong in rollaxis() but
> instead wherever people talk about indexing and/or iterating over an array.
> Nothing about
I agree with Charles that rollaxis() isn't immediately intuitive.
It seems to me that documentation like this doesn't belong in rollaxis()
but instead wherever people talk about indexing and/or iterating over an
array. Nothing about the iteration depends on rollaxis(), rollaxis is
just giving yo
On Thu, Apr 25, 2013 at 9:04 PM, Charles R Harris
wrote:
> After thinking about it, I'm in favor of this small function. Rollaxis takes
> a bit of thought and document reading to figure out how to use it, whereas
> this function covers a common use with an easy to understand API.
It seems to me
19 matches
Mail list logo
