This is so excellent! What a wonderful upgrade to the web-page.
Thank you for all the hard work and effort!
-Travis
On Sun, May 24, 2020 at 7:12 AM Inessa Pawson wrote:
> The NumPy web team is excited to announce the launch of the newly
> redesigned numpy.org. To transform the website into a
On Sun, Mar 22, 2020 at 1:33 PM Sebastian Berg
wrote:
> Hi,
>
> thanks for the feedback!
>
> On Sat, 2020-03-21 at 15:58 -0500, Travis Oliphant wrote:
> > Thanks for publicizing this and all the work that has gone into
> > getting
> > this far.
> &
Thanks for publicizing this and all the work that has gone into getting
this far.
I'm extremely supportive of the foundational DType meta-type and making
dtypes classes. This was the epiphany I had in 2015 that led me to
experiment with xnd and later mtypes. I have not had the funding to work
on
I agree with Stefan that option 2 is what NumPy should go with for .copy()
If you want to get an identical memory copy you should be getting the .data
attribute and doing something with that buffer.
My $0.02
-Travis
On Thu, Apr 11, 2019 at 6:01 PM Stefan van der Walt
wrote:
> Hi Marten,
>
>
Thanks for sharing this work with the world, What you did is not an easy
task. This makes it easier for people to port NumPy-based Python code to
C#. Of course, this group would more likely prefer people to port their C#
code to Python + NumPy.
Nonetheless, I think there are interesting thing
I will be available remotely as well, but unable to come to BIDS this
week.
I am particularly interested in how to improve the dtype subsystem ---
potentially using libndtypes from the xnd project.
Thanks,
-Travis
On Wed, Nov 28, 2018 at 3:16 PM Matti Picus wrote:
> We will be meeting at B
to 1d.
>If the calling code really needed a 1d array, then it will probably
>fail, which is not really different to 2, but has the advantage that the
>names are less surprising.
>4. Only improve the documentation
>
> My preference would be 3
>
> Eric
>
On Fri, Oct 19, 2018 at 8:24 PM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> Hi All,
>
> It seems there are two extreme possibilities for general functions:
> 1. Put `asarray` everywhere. The main benefit that I can see is that even
> if people put in list instead of arrays, one is gu
ansition.
Your bringing the problem of mxnet devs is most appreciated. I will make a
documentation PR.
-Travis
> Alex.
>
>
> 27.10.2018, 02:27, "Travis Oliphant" :
>
> What is the justification for deprecation exactly? These functions have
> been well documente
I see now the original motivation as the unfortunate situation that mxnet
authors did not understand that np.ascontiguousarray returned an array of
at least one dimension and perhaps used that one API to assume that NumPy
did not support 0-d arrays --- which NumPy does indeed support.
Certainly th
What is the justification for deprecation exactly? These functions have
been well documented and have had the intended behavior of producing arrays
with dimension at least 1 for some time. Why is it unexpected to produce
arrays of at least 1 dimension? For some users this is exactly what is
want
I like the proposal generally. NumPy could use a good orthogonal indexing
method and a vectorized-indexing method is fine too.
Robert Kern is spot on with his concerns as well. Please do not change
what arr[idx] does except to provide warnings and perhaps point people to
new .oix and .vix method
On Sun, Jun 17, 2018, 7:48 PM Marten van Kerkwijk
wrote:
> Hi Travis,
>
> More of a detailed question, but as we are currently thinking about
> extending the signature of gufuncs (i.e., things like `(m,n),(n,p)->(m,p)`
> for matrix multiplication), and as you must have thought about this for
> li
Hi everyone,
I'm glad I'm able to contribute back to this discussion thread. I wanted
to post a quick message to this group to make sure there is no
mis-information about XND which has finally reached the point where it can
be experimented with (http://xnd.io) and commented on.
XND came out of t
It is a welcome thing to see Python 2.7 support disappearing.
Dropping 3.4 support in new releases sounds like a great idea as well.
NumPy was originally pitched as a Python 3 thing...
Travis
On Thu, Jun 14, 2018, 12:52 PM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> It seems ever
15 matches
Mail list logo
