[Numpy-discussion] complex_ imported by numexpr, but seems no longer supported by numpy

2023-12-02 Thread
Hi, I'm recently focusing on resolve some of the issues about numexpr and I found that in numexpr's test module, it will run: `from numpy import (, complex_, .)` And when I run `numexpr.test()` the output looks like: Traceback (most recent call last): File "/Users/liuteng/opt/anacond

[Numpy-discussion] Re: complex_ imported by numexpr, but seems no longer supported by numpy

2023-12-06 Thread
So problem solved, I should change the behavior of numexpr.test(). 腾刘 <27rabbi...@gmail.com> 于2023年12月2日周六 16:34写道: > Hi, > > I'm recently focusing on resolve some of the issues about numexpr and I > found that in numexpr's test module, it will run: > > `from nu

[Numpy-discussion] Newbie's naive question about debug

2022-09-07 Thread
Hello, everyone. I'm a newcomer here and looking forward to contributing to Numpy core code in the future. However, there is an obstacle right ahead of me that I don't know how to figure out the corresponding relationship between Numpy python code and its C implementation code. In another word, I

[Numpy-discussion] Re: Newbie's naive question about debug

2022-09-07 Thread
三 21:09写道: > On Wed, Sep 7, 2022, at 07:55, 腾刘 wrote: > > Hello, everyone. I'm a newcomer here and looking forward to > > contributing to Numpy core code in the future. > > > > However, there is an obstacle right ahead of me that I don't know how > > t

[Numpy-discussion] How to avoid this memory copy overhead in d=a*b+c?

2022-09-16 Thread
Hello everyone, I 'm here again to ask a naive question about Numpy performance. As far as I know, Numpy's vectorization operator is very effective because it utilizes SIMD instructions and multi-threads compared to index-style programming (using a "for" loop and assigning each element with its in

[Numpy-discussion] Re: How to avoid this memory copy overhead in d=a*b+c?

2022-09-16 Thread
erators where appropriate to avoid memory allocation. > > > > a *= b > > c += a > > > > Kevin > > > > > > *From: *腾刘 <27rabbi...@gmail.com> > *Sent: *Friday, September 16, 2022 8:35 AM > *To: *Discussion of Numerical Python > *Subject: *[Nu

[Numpy-discussion] Re: How to avoid this memory copy overhead in d=a*b+c?

2022-09-16 Thread
te('a * b + c'). You > could also write a gufunc in numba that would be memory and access > efficient. > > Kevin > > > On Fri, Sep 16, 2022 at 8:53 AM 腾刘 <27rabbi...@gmail.com> wrote: > >> Thanks a lot for answering this question but I still have some

[Numpy-discussion] Re: How to avoid this memory copy overhead in d=a*b+c?

2022-09-16 Thread
e benchmarks (made around 10 years ago, but they > should still apply): > > https://numexpr.readthedocs.io/projects/NumExpr3/en/latest/intro.html#expected-performance > > Cheers > > On Fri, Sep 16, 2022 at 9:57 AM 腾刘 <27rabbi...@gmail.com> wrote: > >> Thanks a

[Numpy-discussion] Confusd about the implementation of @TYPE@_pairwise_sum

2022-09-30 Thread
Hello there, I'm here again. With the help of the previous emails, I finally found out the real C implementation of np.sum(x), where x is a Numpy array. I found that there is a "template" function named @TYPE@_pairwise_sum in numpy/core/src/umath/loops_utils.h.src which is the underlying C code o

[Numpy-discussion] Re: Documentation Team meeting - Monday October 24 at 2pm UTC

2022-10-24 Thread
Hiii~ Have the meeting already re-scheduled to 4pm UTC? I found nobody there. Melissa Mendonça 于2022年10月24日周一 08:05写道: > > Hi all! > > Our next Documentation Team meeting will happen on *Monday, October 24* at > ***2PM UTC***. (We are also considering moving this meeting to its > original time

[Numpy-discussion] Re: Documentation Team meeting - Monday October 24 at 2pm UTC

2022-10-24 Thread
s related to contributing or > improving the official NumPy documentation, feel free to ask them here, on > the mailing list, or in the #docs channel on the NumPy workspace. > > On Mon, Oct 24, 2022 at 10:22 AM 腾刘 <27rabbi...@gmail.com> wrote: > >> Hiii~ >> >>

[Numpy-discussion] Re: Documentation Team meeting - Monday October 24 at 2pm UTC

2022-10-25 Thread
ou all updated for next time. But the > plan is to move it to 4pm UTC starting next time, November 7. > > Best, > > Melissa > > On Mon, Oct 24, 2022 at 12:35 PM 腾刘 <27rabbi...@gmail.com> wrote: > >> Seems that the link is broken. Because it is

[Numpy-discussion] Re: next NumPy Newcomers' Hour - 12 pm UTC

2022-10-30 Thread
wow it's 8 in the morning, very energetic period of time Inessa Pawson 于2022年10月30日周日 15:24写道: > Our next Newcomers' Hour will be held this Thursday, November 3rd, at 12 > pm UTC. (Please note the new time that is friendly for those who are in the > eastern hemisphere!) Stop by to ask questions

[Numpy-discussion] How does Numpy build system detect the change of .c source file?

2022-11-02 Thread
Hi everyone! I 'm here again. Recently I 'm trying to understand the C code with output-debug method, inserting many print statements. I was doing well with it until one day: I changed a file called loops_utils.h.src located in numpy/core/src/umath by inserting some "printf", but after I re-built

[Numpy-discussion] Re: How does Numpy build system detect the change of .c source file?

2022-11-02 Thread
So much thanks! I will have a look at how distutils work and try to figure out whether I can fix this dependency problem. Ralf Gommers 于2022年11月2日周三 17:13写道: > > > On Wed, Nov 2, 2022 at 9:30 AM 腾刘 <27rabbi...@gmail.com> wrote: > >> Hi everyone! I 'm here again.

[Numpy-discussion] Re: ANN: NumPy Fellowship Program & Sayed Adel as our first Developer in Residence

2022-12-02 Thread
congrats! Ross Barnowski 于2022年12月2日周五 23:45写道: > This developer-in-residence program is an excellent idea, many thanks to > everyone who helped launch the initiative. > > Congratulations Sayed! > > ~Ross > > On Fri, Dec 2, 2022 at 5:04 AM Julien Jerphanion wrote: > >> Congratulations to all t