[Numpy-discussion] Re: Moving community meeting to 16:00 UTC
thanks for sharing such informative blog .https://bit.ly/3lAUgg7 ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: moving the time of community meetings
your post is really informative and interesting . https://bit.ly/3lAUgg7 ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: np.trunc is inconsistent with array-api
thanks for sharing such informative blog. https://bit.ly/3lAUgg7 ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: NumPy Development Meeting Wednesday - Triage Focus
your blog are really interesting and informative .https://bit.ly/3lAUgg7 ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Running numpy.test() after pip install
I just installed NumPy using pip and Python 3.9.7 on CentOS 7.9. Installation went fine, but when I ran >>> import numpy >>> numpy.test() I got a traceback, and this summary. === short test summary info ERROR - ModuleNotFoundError: No module named 'hypothesis' Interrupted: 1 error during collection It seems that both hypothesis and pytest are needed to run numpy.test(). We like to be able to run all the tests even after a pip install, and being able to run some of the tests from pip-installed numpy is useful as well. May I suggest you add those two packages as dependencies for NumPy at PyPi? Neither are particularly large, both are generally useful, and I think the potential utility for those who would ike to check on their own system for anomalies outweighs the minimal impact on the majority of users who would not use it but would also probably not notice their presence. If adding them as dependencies seems to heavy weight, or is otherwised deemed undesirable, perhaps just a note in the Project Description at https://pypi.org/project/numpy/ to say that, if you want to run tests, those two packages will be needed? Thanks,-- bennet ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Running numpy.test() after pip install
I think NumPy has always tried to have effectively no install dependencies at least when installed from source (minimal install from git only requires Cython). This seems like a good goal to me and there are scenarios where extra packages are a burden (e.g., Amazon Lambda). AFAICT pretty much every package in the numerical python ecosystem excludes test dependencies from setup requires or install requires. Kevin From: Bennet FauberSent: Tuesday, September 28, 2021 6:00 PMTo: numpy-discussion@python.orgSubject: [Numpy-discussion] Running numpy.test() after pip install I just installed NumPy using pip and Python 3.9.7 on CentOS 7.9.Installation went fine, but when I ran >>> import numpy>>> numpy.test() I got a traceback, and this summary. === short test summary info ERROR - ModuleNotFoundError: No module named 'hypothesis' Interrupted: 1 error during collection It seems that both hypothesis and pytest are needed to run numpy.test(). We like to be able to run all the tests even after a pip install, andbeing able to run some of the tests from pip-installed numpy is usefulas well. May I suggest you add those two packages as dependencies for NumPy atPyPi? Neither are particularly large, both are generally useful, andI think the potential utility for those who would ike to check ontheir own system for anomalies outweighs the minimal impact on themajority of users who would not use it but would also probably notnotice their presence. If adding them as dependencies seems to heavy weight, or is otherwiseddeemed undesirable, perhaps just a note in the Project Description athttps://pypi.org/project/numpy/ to say that, if you want to run tests,those two packages will be needed? Thanks, -- bennet___NumPy-Discussion mailing list -- numpy-discussion@python.orgTo unsubscribe send an email to numpy-discussion-le...@python.orghttps://mail.python.org/mailman3/lists/numpy-discussion.python.org/Member address: kevin.k.shepp...@gmail.com ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Moving community meeting to 16:00 UTC
On Wed, 2021-09-22 at 21:11 +0200, Ralf Gommers wrote: > On Wed, Sep 22, 2021 at 8:31 PM Sebastian Berg < > sebast...@sipsolutions.net> > wrote: > > > Hi all, > > > > Melissa brought up that we should reschedule the bi-weekly > > community > > meeting to the same time slot at the triage meeting: > > > > Wednesdays 16:00 UTC (9 am Pacific time) [1] > > > > This will simplify attending for those in Europe and allow a more > > reasonable time including for India. > > > > As of now, all regular attendees are happy with this move. > > > I have a structural conflict at that time, I'd only be able to make > the > second half of the meeting. > > Perhaps we could make it 16:30 UTC (= 10pm in India), or otherwise > 15:00 or > 16:00 UTC on Tuesdays? > Sorry about that, lets go with 16:30 UTC then, at least for now. I will announce that later for tomorrow. If that ends up bad for anyone (or the situation just changes) we can still move it. Cheers, Sebastian > But the original idea was that we could also alternate between two > times, > > the > > current time is e.g. impossible to make from east Asia. > > > > Yes, the current time is very late and was only chosen to make it 6am > in > Australia (which is no longer needed) - we should move it forward > even if > we end up alternating between two times. > > Cheers, > Ralf > > > > > Please let me/us know if you prefer a different schedule now (or > > later!). The idea is that these meetings are accessible to anyone > > interested. > > Without any comments, I will announce and change the calendar > > starting > > with next weeks meeting. > > > > Cheers, > > > > Sebastian > > > > > > > > [1] I have to see whether we will stick with UTC or do any daylight > > savings. > > ___ > > NumPy-Discussion mailing list -- numpy-discussion@python.org > > To unsubscribe send an email to numpy-discussion-le...@python.org > > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > > Member address: ralf.gomm...@googlemail.com > > > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: sebast...@sipsolutions.net signature.asc Description: This is a digitally signed message part ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Moving community meeting to 16:00 UTC
On Tue, Sep 28, 2021 at 7:20 PM Sebastian Berg wrote: > On Wed, 2021-09-22 at 21:11 +0200, Ralf Gommers wrote: > > On Wed, Sep 22, 2021 at 8:31 PM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > Hi all, > > > > > > Melissa brought up that we should reschedule the bi-weekly > > > community > > > meeting to the same time slot at the triage meeting: > > > > > > Wednesdays 16:00 UTC (9 am Pacific time) [1] > > > > > > This will simplify attending for those in Europe and allow a more > > > reasonable time including for India. > > > > > > As of now, all regular attendees are happy with this move. > > > > > > I have a structural conflict at that time, I'd only be able to make > > the > > second half of the meeting. > > > > Perhaps we could make it 16:30 UTC (= 10pm in India), or otherwise > > 15:00 or > > 16:00 UTC on Tuesdays? > > > > Sorry about that, lets go with 16:30 UTC then, at least for now. I > will announce that later for tomorrow. If that ends up bad for anyone > (or the situation just changes) we can still move it. > Thanks! Ralf > Cheers, > > Sebastian > > > > > But the original idea was that we could also alternate between two > > times, > > > the > > > current time is e.g. impossible to make from east Asia. > > > > > > > Yes, the current time is very late and was only chosen to make it 6am > > in > > Australia (which is no longer needed) - we should move it forward > > even if > > we end up alternating between two times. > > > > Cheers, > > Ralf > > > > > > > > > Please let me/us know if you prefer a different schedule now (or > > > later!). The idea is that these meetings are accessible to anyone > > > interested. > > > Without any comments, I will announce and change the calendar > > > starting > > > with next weeks meeting. > > > > > > Cheers, > > > > > > Sebastian > > > > > > > > > > > > [1] I have to see whether we will stick with UTC or do any daylight > > > savings. > > > ___ > > > NumPy-Discussion mailing list -- numpy-discussion@python.org > > > To unsubscribe send an email to numpy-discussion-le...@python.org > > > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > > > Member address: ralf.gomm...@googlemail.com > > > > > ___ > > NumPy-Discussion mailing list -- numpy-discussion@python.org > > To unsubscribe send an email to numpy-discussion-le...@python.org > > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > > Member address: sebast...@sipsolutions.net > > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: ralf.gomm...@gmail.com > ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Running numpy.test() after pip install
On Tue, Sep 28, 2021 at 7:07 PM Kevin Sheppard wrote: > I think NumPy has always tried to have effectively no install dependencies > at least when installed from source (minimal install from git only requires > Cython). This seems like a good goal to me and there are scenarios where > extra packages are a burden (e.g., Amazon Lambda). AFAICT pretty much > every package in the numerical python ecosystem excludes test dependencies > from setup requires or install requires. > Agreed. We don't want to make any changes here, if you want to run the tests you can just install pytest and hypothesis. Cheers, Ralf > > Kevin > > > > > > *From: *Bennet Fauber > *Sent: *Tuesday, September 28, 2021 6:00 PM > *To: *numpy-discussion@python.org > *Subject: *[Numpy-discussion] Running numpy.test() after pip install > > > > I just installed NumPy using pip and Python 3.9.7 on CentOS 7.9. > > Installation went fine, but when I ran > > > > >>> import numpy > > >>> numpy.test() > > > > I got a traceback, and this summary. > > > > === short test summary info > > > ERROR - ModuleNotFoundError: No module named 'hypothesis' > > Interrupted: 1 error during collection > > > > > It seems that both hypothesis and pytest are needed to run numpy.test(). > > > > We like to be able to run all the tests even after a pip install, and > > being able to run some of the tests from pip-installed numpy is useful > > as well. > > > > May I suggest you add those two packages as dependencies for NumPy at > > PyPi? Neither are particularly large, both are generally useful, and > > I think the potential utility for those who would ike to check on > > their own system for anomalies outweighs the minimal impact on the > > majority of users who would not use it but would also probably not > > notice their presence. > > > > If adding them as dependencies seems to heavy weight, or is otherwised > > deemed undesirable, perhaps just a note in the Project Description at > > https://pypi.org/project/numpy/ to say that, if you want to run tests, > > those two packages will be needed? > > > > Thanks,-- bennet > > ___ > > NumPy-Discussion mailing list -- numpy-discussion@python.org > > To unsubscribe send an email to numpy-discussion-le...@python.org > > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > > Member address: kevin.k.shepp...@gmail.com > > > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: ralf.gomm...@gmail.com > ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Running numpy.test() after pip install
Could numpy include a variant (I'm not sure what setuptools calls this) so that 'pip install numpy[tests]' installs those extra dependencies? Aaron Meurer On Tue, Sep 28, 2021 at 11:33 AM Ralf Gommers wrote: > > > > On Tue, Sep 28, 2021 at 7:07 PM Kevin Sheppard > wrote: >> >> I think NumPy has always tried to have effectively no install dependencies >> at least when installed from source (minimal install from git only requires >> Cython). This seems like a good goal to me and there are scenarios where >> extra packages are a burden (e.g., Amazon Lambda). AFAICT pretty much every >> package in the numerical python ecosystem excludes test dependencies from >> setup requires or install requires. > > > Agreed. We don't want to make any changes here, if you want to run the tests > you can just install pytest and hypothesis. > > Cheers, > Ralf > >> >> >> Kevin >> >> >> >> >> >> From: Bennet Fauber >> Sent: Tuesday, September 28, 2021 6:00 PM >> To: numpy-discussion@python.org >> Subject: [Numpy-discussion] Running numpy.test() after pip install >> >> >> >> I just installed NumPy using pip and Python 3.9.7 on CentOS 7.9. >> >> Installation went fine, but when I ran >> >> >> >> >>> import numpy >> >> >>> numpy.test() >> >> >> >> I got a traceback, and this summary. >> >> >> >> === short test summary info >> >> >> ERROR - ModuleNotFoundError: No module named 'hypothesis' >> >> Interrupted: 1 error during collection >> >> >> >> >> It seems that both hypothesis and pytest are needed to run numpy.test(). >> >> >> >> We like to be able to run all the tests even after a pip install, and >> >> being able to run some of the tests from pip-installed numpy is useful >> >> as well. >> >> >> >> May I suggest you add those two packages as dependencies for NumPy at >> >> PyPi? Neither are particularly large, both are generally useful, and >> >> I think the potential utility for those who would ike to check on >> >> their own system for anomalies outweighs the minimal impact on the >> >> majority of users who would not use it but would also probably not >> >> notice their presence. >> >> >> >> If adding them as dependencies seems to heavy weight, or is otherwised >> >> deemed undesirable, perhaps just a note in the Project Description at >> >> https://pypi.org/project/numpy/ to say that, if you want to run tests, >> >> those two packages will be needed? >> >> >> >> Thanks,-- bennet >> >> ___ >> >> NumPy-Discussion mailing list -- numpy-discussion@python.org >> >> To unsubscribe send an email to numpy-discussion-le...@python.org >> >> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ >> >> Member address: kevin.k.shepp...@gmail.com >> >> >> >> ___ >> NumPy-Discussion mailing list -- numpy-discussion@python.org >> To unsubscribe send an email to numpy-discussion-le...@python.org >> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ >> Member address: ralf.gomm...@gmail.com > > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: asmeu...@gmail.com ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: Moving community meeting to 16:00 UTC
On Tue, Sep 28, 2021 at 7:20 PM Sebastian Berg mailto:sebast...@sipsolutions.net>> wrote: Sorry about that, lets go with 16:30 UTC then, at least for now. I will announce that later for tomorrow. If that ends up bad for anyone (or the situation just changes) we can still move it. Could someone modify the community calendar appropriately? Thanks, Matti ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: A bite of C++
On Wed, 2021-08-25 at 17:48 +0200, Serge Guelton wrote:
> Hi folks,
>
> https://github.com/numpy/numpy/pull/19713 showcases what *could* be a
> first step
> toward getting rid of generated C code within numpy, in favor of some
> C++ code,
> coupled with a single macro trick.
It seems time to pick up this discussion again. I think we were
cautiously in favor of trying this out in the limited proposed form.
Aside from ensuring we do not use C++ exceptions/run-time environment.
I.e. compile with `-fno-exception` and `-nostdlib`, the PR is probably
largely ready.
Are there any other bigger issues that need to be discussed?
The goal for now seems to allow this type of function templates (C++ as
a glorified templating language). We may be able to enforce this with
clang-tidy (not sure if that is necessary right away though).
There are parts of NumPy (mainly `fft`) where more C++ features could
be helpful but that should probably be discussed separately.
The current solution ends up using no X-Macro anymore, which means
listing the C symbols like:
NPY_NO_EXPORT int radixsort_byte(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
NPY_NO_EXPORT int radixsort_ubyte(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
NPY_NO_EXPORT int radixsort_short(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
NPY_NO_EXPORT int radixsort_ushort(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
NPY_NO_EXPORT int radixsort_int(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
NPY_NO_EXPORT int radixsort_uint(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
NPY_NO_EXPORT int radixsort_long(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
NPY_NO_EXPORT int radixsort_ulong(void* vec, npy_intp cnt, void
*NPY_UNUSED(null)) { return radixsort(vec, cnt); }
I guess we could try to write some macro's to make this shorter,
although I am fine with delaying this, since the main point is probably
getting a brief example and the build changes in.
It also defines the following type tags:
https://github.com/numpy/numpy/pull/19713/files#diff-4de4beaecd7b0a1f4d887221191843a54b0c62f13eea18b8716c54bec9657f20
Any comments to the approach (especially from anyone more familiar with
C++) would be much appreciated!
Cheers,
Sebastian
>
> Basically, templated code is an easy and robust way to replace
> generated code
> (the C++ compiler becomes the code generator when instantiating
> code), and a
> single X-macro takes care of the glue with the C world.
>
> Some changes in distutils were needed to cope with C++-specific
> flags, and
> extensions that consist in mixed C and C++ code.
>
> I've kept the change as minimal as possible to ease the (potential)
> transition
> and keep the C++ code close to the C code. This led to less idiomatic
> C++ code,
> but I value a "correct first" approach. There's an on-going effort by
> seiko2plus
> to remove that C layer, I acknowledge this would bring even more C++
> code, but
> that looks orthogonal to me (and a very good second step!)
>
> All lights are green for the PR, let's assume it's a solid ground for
> discussion :-)
> So, well, what do you think? Should we go forward?
>
> Potential follow-ups :
>
> - do we want to use -nostdlib, to be sure we don't bring any C++
> runtime dep?
> - what about -fno-exception, -fno-rtti?
> - coding style?
> - (I'm-not-a-farseer-I-don-t-know-all-topics)
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
signature.asc
Description: This is a digitally signed message part
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com
[Numpy-discussion] NumPy Community Meeting Wednesday (earlier @16:30 UTC!)
Hi all, There will be a NumPy Community meeting Wednesday September 29th at 16:30 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian NOTE: The time is different from previous meetings which had started at 18:00 UTC. signature.asc Description: This is a digitally signed message part ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: A bite of C++
Looks like a new world record and a satisfactory efforts! https://bit.ly/3EVg4Ma ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
