[Numpy-discussion] Re: Behavior of round(array)

[Aaron Meurer]

On Wed, Nov 30, 2022 at 10:39 AM Sebastian Berg
 wrote:
>
> Hi all,
>
> there is a discussion about how `round(array)` should behave in:
>
> https://github.com/numpy/numpy/issues/6248
>
> There is some discussion about object arrays which should probably be
> fixed for `around()` in that ago.
>
> Otherwise, the is the question what to do about the fact that:
>
> * round(np.float64(2.**64))  -> 18446744073709551616  (a Python int)
> * round(np.array([2., 3., 2.**64])  can only return float or integer
>
> The NumPy `np.round`/`np.around` (same function) functions always
> return the same dtype.
>
> We can either ignore that discrepancy, or opt to raise an error, so
> that:
>
> >>> round(np.array([2., 3.5]))
> TypeError: Rounding a NumPy float array cannot return integers,
> use `round(arr, ndigits=0)` or `round(arr, 0) to indicate that a
> float result is desired.
>
> In the call today, I think we leaned a bit towards ignoring it, but if
> I read Aaron correctly, he prefers the error and it may be the
> conservative choice.

I guess I weakly prefer it, but I mostly just suggested it because it
is the conservative option. Making ndigits=None just match ndigits=0
(so that round() works like around()) is also fine IMO. I don't think
it would be too surprising for most people to have round() work that
way on arrays.

What I feel more strongly about is that there shouldn't be distinct
behavior for scalars vs. arrays, and the output dtype shouldn't be
value-based.

Aaron Meurer

>
> We could of course do other things (i.e. return an integer `intp`
> array) but that would probably require a hard error for overflows
> (which is different from `np.rint(arr).astype(np.intp)`.
>
> Are there any small or big opinions on this?  It seems useful to enable
> `round()` and is a bit of a shame to get caught up on the detail, but I
> am not sure what the right choice is :).
>
> - Sebastian
>
> ___
> 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] ANN: NumPy Fellowship Program & Sayed Adel as our first Developer in Residence

[Ralf Gommers]

Hi all,

I'm excited to be able to share this announcement on behalf of the NumPy
Steering Council. We have created a new program, the NumPy Fellowship
Program, and offered Sayed Adel the very first Developer in Residence role.
Sayed starts his 1 year tenure in that role today, and we are really
looking forward to him working on NumPy full-time.

We wrote a blog post about the program, and why we offered the role to
Sayed: https://blog.scientific-python.org/numpy/fellowship-program/. I've
copied the blog post content at the end of this email.

In addition, here is some more detail on NumPy project finances that didn't
make it into the blog post (which is likely to have a wider audience than
the readership of this mailing list), but is quite relevant to share here:

Over the past decade, NumPy has accumulated individual donations as well as
payments from Tidelift. NumPy has been a fiscally sponsored project of
NumFOCUS for a decade - meaning that NumFOCUS, as a 501(c)3 nonprofit,
administers funds for NumPy. As a result, NumPy has accumulated funds for a
long time - and those are now transparently administered on Open Collective
. There you will see a "general fund",
currently with a ~$23,000 balance, and two open "projects" with committed
funding - one for the active CZI grant we have, and one for this new
Fellowship Program. Guidelines for using those funds are described in
https://numpy.org/neps/nep-0048-spending-project-funds.html.

Finally it is worth pointing out that we are now able to solicit donations
on Open Collective, and have added contribution tiers on the front page of
https://opencollective.com/numpy. Until now, we have never actively
solicited donations as a project, because the accounting support and
transparent financial reporting was not in place. That has changed now
though, so we are hoping that with guidelines to spend funds plus a
concrete fellowship program that we're expecting to be quite impactful, we
are now able to confidently tell people that if they donate to NumPy, we
will manage their contribution well and translate it into more time for
someone on the NumPy team to make NumPy better.

Cheers,
Ralf


blog post content:

The NumPy team is excited to announce the launch of the NumPy Fellowship
Program and the appointment of Sayed Adel (@seiko2plus) as the first NumPy
Developer in Residence. This is a significant milestone in the history of
the project: for the first time, NumPy is in a position to use its project
funds to pay for a full year of maintainer time. We believe that this will
be an impactful program that will contribute to NumPy’s long-term
sustainability as a community-driven open source project.

Sayed has been making major contributions to NumPy since the start of 2020,
in particular around computational performance. He is the main author of
the NumPy SIMD architecture (NEP 38, docs), generously shared his knowledge
of SIMD instructions with the core developer team, and helped integrate the
work of various volunteer and industry contributors in this area. As a
result, we’ve been able to expand support to multiple CPU architectures,
integrating contributions from IBM, Intel, Apple, and others, none of which
would have been possible without Sayed. Furthermore, when NumPy tentatively
started using C++ in 2021, Sayed was one of the proponents of the move and
helped with its implementation.

The NumPy Steering Council sees Sayed’s appointment to this role as both
recognition of his past outstanding contributions as well as an opportunity
to continue improving NumPy’s computational performance. In the next 12
months, we’d like to see Sayed focus on the following:

SIMD code maintenance,
code review of SIMD contributions from others,
performance-related features,
sharing SIMD and C++ expertise with the team and growing a NumPy
sub-team around it,
SIMD build system migration to Meson,
and wherever else Sayed’s interests take him.

“I’m both happy and nervous: this is a great opportunity, but also a
great responsibility,” said Sayed in response to his appointment.

The funds for the NumPy Fellowship Program come from a partnership with
Tidelift and from individual donations. We sincerely thank both Tidelift
and everyone who donated to the project—without you, this program would not
be possible! We also acknowledge the CPython Developer-in-Residence and the
Django Fellowship programs, which served as inspiration for this program.

Sayed officially starts as the NumPy Developer in Residence today, 1
December 2022. Already, we are thinking about opportunities beyond this
first year: we imagine “in residence” roles that focus on developing,
improving, and maintaining other parts of the NumPy project (e.g.,
documentation, website, translations, contributor experience, etc.). We
look forward to this exciting new chapter of the NumPy contributor
community and will keep you posted on our progress.
_

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

[Stefan van der Walt]

On Thu, Dec 1, 2022, at 13:17, Ralf Gommers wrote:
> I'm excited to be able to share this announcement on behalf of the NumPy 
> Steering Council. We have created a new program, the NumPy Fellowship 
> Program, and offered Sayed Adel the very first Developer in Residence role. 
> Sayed starts his 1 year tenure in that role today, and we are really looking 
> forward to him working on NumPy full-time.

This is a celebration-worthy milestone for the project: thank you to everyone 
who worked to make it possible!

> so we are hoping that with guidelines to spend funds plus a concrete 
> fellowship program that we're expecting to be quite impactful, we are now 
> able to confidently tell people that if they donate to NumPy, we will manage 
> their contribution well and translate it into more time for someone on the 
> NumPy team to make NumPy better.

There are a lot of moving pieces here; thank you for getting them all in place. 
 It feels great being able to invite financial contributions, knowing how they 
will be spent!

Stéfan
___
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: ANN: NumPy Fellowship Program & Sayed Adel as our first Developer in Residence

[Stefan van der Walt]

On Thu, Dec 1, 2022, at 13:27, Stefan van der Walt wrote:
> On Thu, Dec 1, 2022, at 13:17, Ralf Gommers wrote:
>> I'm excited to be able to share this announcement on behalf of the NumPy 
>> Steering Council. We have created a new program, the NumPy Fellowship 
>> Program, and offered Sayed Adel the very first Developer in Residence role. 
>> Sayed starts his 1 year tenure in that role today, and we are really looking 
>> forward to him working on NumPy full-time.
> 
> This is a celebration-worthy milestone for the project: thank you to everyone 
> who worked to make it possible!

Sorry for another email, but how can I miss this: congratulations, Sayed, on 
your new role.  We're so happy to have you on board!

Stéfan
___
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: ANN: NumPy Fellowship Program & Sayed Adel as our first Developer in Residence

[Brigitta Sipőcz]

Wonderful news, congratulations Sayed!

Brigitta

On Thu, 1 Dec 2022 at 13:18, Ralf Gommers  wrote:

> Hi all,
>
> I'm excited to be able to share this announcement on behalf of the NumPy
> Steering Council. We have created a new program, the NumPy Fellowship
> Program, and offered Sayed Adel the very first Developer in Residence role.
> Sayed starts his 1 year tenure in that role today, and we are really
> looking forward to him working on NumPy full-time.
>
> We wrote a blog post about the program, and why we offered the role to
> Sayed: https://blog.scientific-python.org/numpy/fellowship-program/. I've
> copied the blog post content at the end of this email.
>
> In addition, here is some more detail on NumPy project finances that
> didn't make it into the blog post (which is likely to have a wider audience
> than the readership of this mailing list), but is quite relevant to share
> here:
>
> Over the past decade, NumPy has accumulated individual donations as well
> as payments from Tidelift. NumPy has been a fiscally sponsored project of
> NumFOCUS for a decade - meaning that NumFOCUS, as a 501(c)3 nonprofit,
> administers funds for NumPy. As a result, NumPy has accumulated funds for a
> long time - and those are now transparently administered on Open
> Collective . There you will see a
> "general fund", currently with a ~$23,000 balance, and two open "projects"
> with committed funding - one for the active CZI grant we have, and one for
> this new Fellowship Program. Guidelines for using those funds are described
> in https://numpy.org/neps/nep-0048-spending-project-funds.html.
>
> Finally it is worth pointing out that we are now able to solicit donations
> on Open Collective, and have added contribution tiers on the front page of
> https://opencollective.com/numpy. Until now, we have never actively
> solicited donations as a project, because the accounting support and
> transparent financial reporting was not in place. That has changed now
> though, so we are hoping that with guidelines to spend funds plus a
> concrete fellowship program that we're expecting to be quite impactful, we
> are now able to confidently tell people that if they donate to NumPy, we
> will manage their contribution well and translate it into more time for
> someone on the NumPy team to make NumPy better.
>
> Cheers,
> Ralf
>
>
> blog post content:
>
> The NumPy team is excited to announce the launch of the NumPy Fellowship
> Program and the appointment of Sayed Adel (@seiko2plus) as the first NumPy
> Developer in Residence. This is a significant milestone in the history of
> the project: for the first time, NumPy is in a position to use its project
> funds to pay for a full year of maintainer time. We believe that this will
> be an impactful program that will contribute to NumPy’s long-term
> sustainability as a community-driven open source project.
>
> Sayed has been making major contributions to NumPy since the start of
> 2020, in particular around computational performance. He is the main author
> of the NumPy SIMD architecture (NEP 38, docs), generously shared his
> knowledge of SIMD instructions with the core developer team, and helped
> integrate the work of various volunteer and industry contributors in this
> area. As a result, we’ve been able to expand support to multiple CPU
> architectures, integrating contributions from IBM, Intel, Apple, and
> others, none of which would have been possible without Sayed. Furthermore,
> when NumPy tentatively started using C++ in 2021, Sayed was one of the
> proponents of the move and helped with its implementation.
>
> The NumPy Steering Council sees Sayed’s appointment to this role as both
> recognition of his past outstanding contributions as well as an opportunity
> to continue improving NumPy’s computational performance. In the next 12
> months, we’d like to see Sayed focus on the following:
>
> SIMD code maintenance,
> code review of SIMD contributions from others,
> performance-related features,
> sharing SIMD and C++ expertise with the team and growing a NumPy
> sub-team around it,
> SIMD build system migration to Meson,
> and wherever else Sayed’s interests take him.
>
> “I’m both happy and nervous: this is a great opportunity, but also a
> great responsibility,” said Sayed in response to his appointment.
>
> The funds for the NumPy Fellowship Program come from a partnership with
> Tidelift and from individual donations. We sincerely thank both Tidelift
> and everyone who donated to the project—without you, this program would not
> be possible! We also acknowledge the CPython Developer-in-Residence and the
> Django Fellowship programs, which served as inspiration for this program.
>
> Sayed officially starts as the NumPy Developer in Residence today, 1
> December 2022. Already, we are thinking about opportunities beyond this
> first year: we imagine “in residence” roles that focus on developing,
> improving, an

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

[Sayed Adel]

I feel delighted and more motivated to work. I am now working on 
accepting the new reality and organize the tasks entrusted to me. Thanks 
to the NumPy team who supported me from the beginning until now.


Thanks, Sayed.

On 12/2/22 01:03, Brigitta Sipőcz wrote:

Wonderful news, congratulations Sayed!

Brigitta

On Thu, 1 Dec 2022 at 13:18, Ralf Gommers  wrote:

Hi all,

I'm excited to be able to share this announcement on behalf of the
NumPy Steering Council. We have created a new program, the NumPy
Fellowship Program, and offered Sayed Adel the very first
Developer in Residence role. Sayed starts his 1 year tenure in
that role today, and we are really looking forward to him working
on NumPy full-time.

We wrote a blog post about the program, and why we offered the
role to Sayed:
https://blog.scientific-python.org/numpy/fellowship-program/. I've
copied the blog post content at the end of this email.

In addition, here is some more detail on NumPy project finances
that didn't make it into the blog post (which is likely to have a
wider audience than the readership of this mailing list), but is
quite relevant to share here:

Over the past decade, NumPy has accumulated individual donations
as well as payments from Tidelift. NumPy has been a fiscally
sponsored project of NumFOCUS for a decade - meaning that
NumFOCUS, as a 501(c)3 nonprofit, administers funds for NumPy. As
a result, NumPy has accumulated funds for a long time - and those
are now transparently administered on Open Collective
. There you will see a "general
fund", currently with a ~$23,000 balance, and two open "projects"
with committed funding - one for the active CZI grant we have, and
one for this new Fellowship Program. Guidelines for using those
funds are described in
https://numpy.org/neps/nep-0048-spending-project-funds.html.

Finally it is worth pointing out that we are now able to solicit
donations on Open Collective, and have added contribution tiers on
the front page of https://opencollective.com/numpy. Until now, we
have never actively solicited donations as a project, because the
accounting support and transparent financial reporting was not in
place. That has changed now though, so we are hoping that with
guidelines to spend funds plus a concrete fellowship program that
we're expecting to be quite impactful, we are now able to
confidently tell people that if they donate to NumPy, we will
manage their contribution well and translate it into more time for
someone on the NumPy team to make NumPy better.

Cheers,
Ralf


blog post content:

The NumPy team is excited to announce the launch of the NumPy
Fellowship Program and the appointment of Sayed Adel (@seiko2plus)
as the first NumPy Developer in Residence. This is a significant
milestone in the history of the project: for the first time, NumPy
is in a position to use its project funds to pay for a full year
of maintainer time. We believe that this will be an impactful
program that will contribute to NumPy’s long-term sustainability
as a community-driven open source project.

Sayed has been making major contributions to NumPy since the start
of 2020, in particular around computational performance. He is the
main author of the NumPy SIMD architecture (NEP 38, docs),
generously shared his knowledge of SIMD instructions with the core
developer team, and helped integrate the work of various volunteer
and industry contributors in this area. As a result, we’ve been
able to expand support to multiple CPU architectures, integrating
contributions from IBM, Intel, Apple, and others, none of which
would have been possible without Sayed. Furthermore, when NumPy
tentatively started using C++ in 2021, Sayed was one of the
proponents of the move and helped with its implementation.

The NumPy Steering Council sees Sayed’s appointment to this role
as both recognition of his past outstanding contributions as well
as an opportunity to continue improving NumPy’s computational
performance. In the next 12 months, we’d like to see Sayed focus
on the following:

    SIMD code maintenance,
    code review of SIMD contributions from others,
    performance-related features,
    sharing SIMD and C++ expertise with the team and growing a
NumPy sub-team around it,
    SIMD build system migration to Meson,
    and wherever else Sayed’s interests take him.

    “I’m both happy and nervous: this is a great opportunity, but
also a great responsibility,” said Sayed in response to his
appointment.

The funds for the NumPy Fellowship Program come from a partnership
with Tidelift and from individual donations. We sincerely thank
both Tidelift and everyone who donated to the project

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

[Evgeni Burovski]

Congratulations Sayed!

On Fri, Dec 2, 2022 at 2:05 AM Brigitta Sipőcz
 wrote:
>
> Wonderful news, congratulations Sayed!
>
> Brigitta
>
> On Thu, 1 Dec 2022 at 13:18, Ralf Gommers  wrote:
>>
>> Hi all,
>>
>> I'm excited to be able to share this announcement on behalf of the NumPy 
>> Steering Council. We have created a new program, the NumPy Fellowship 
>> Program, and offered Sayed Adel the very first Developer in Residence role. 
>> Sayed starts his 1 year tenure in that role today, and we are really looking 
>> forward to him working on NumPy full-time.
>>
>> We wrote a blog post about the program, and why we offered the role to 
>> Sayed: https://blog.scientific-python.org/numpy/fellowship-program/. I've 
>> copied the blog post content at the end of this email.
>>
>> In addition, here is some more detail on NumPy project finances that didn't 
>> make it into the blog post (which is likely to have a wider audience than 
>> the readership of this mailing list), but is quite relevant to share here:
>>
>> Over the past decade, NumPy has accumulated individual donations as well as 
>> payments from Tidelift. NumPy has been a fiscally sponsored project of 
>> NumFOCUS for a decade - meaning that NumFOCUS, as a 501(c)3 nonprofit, 
>> administers funds for NumPy. As a result, NumPy has accumulated funds for a 
>> long time - and those are now transparently administered on Open Collective. 
>> There you will see a "general fund", currently with a ~$23,000 balance, and 
>> two open "projects" with committed funding - one for the active CZI grant we 
>> have, and one for this new Fellowship Program. Guidelines for using those 
>> funds are described in 
>> https://numpy.org/neps/nep-0048-spending-project-funds.html.
>>
>> Finally it is worth pointing out that we are now able to solicit donations 
>> on Open Collective, and have added contribution tiers on the front page of 
>> https://opencollective.com/numpy. Until now, we have never actively 
>> solicited donations as a project, because the accounting support and 
>> transparent financial reporting was not in place. That has changed now 
>> though, so we are hoping that with guidelines to spend funds plus a concrete 
>> fellowship program that we're expecting to be quite impactful, we are now 
>> able to confidently tell people that if they donate to NumPy, we will manage 
>> their contribution well and translate it into more time for someone on the 
>> NumPy team to make NumPy better.
>>
>> Cheers,
>> Ralf
>>
>>
>> blog post content:
>>
>> The NumPy team is excited to announce the launch of the NumPy Fellowship 
>> Program and the appointment of Sayed Adel (@seiko2plus) as the first NumPy 
>> Developer in Residence. This is a significant milestone in the history of 
>> the project: for the first time, NumPy is in a position to use its project 
>> funds to pay for a full year of maintainer time. We believe that this will 
>> be an impactful program that will contribute to NumPy’s long-term 
>> sustainability as a community-driven open source project.
>>
>> Sayed has been making major contributions to NumPy since the start of 2020, 
>> in particular around computational performance. He is the main author of the 
>> NumPy SIMD architecture (NEP 38, docs), generously shared his knowledge of 
>> SIMD instructions with the core developer team, and helped integrate the 
>> work of various volunteer and industry contributors in this area. As a 
>> result, we’ve been able to expand support to multiple CPU architectures, 
>> integrating contributions from IBM, Intel, Apple, and others, none of which 
>> would have been possible without Sayed. Furthermore, when NumPy tentatively 
>> started using C++ in 2021, Sayed was one of the proponents of the move and 
>> helped with its implementation.
>>
>> The NumPy Steering Council sees Sayed’s appointment to this role as both 
>> recognition of his past outstanding contributions as well as an opportunity 
>> to continue improving NumPy’s computational performance. In the next 12 
>> months, we’d like to see Sayed focus on the following:
>>
>> SIMD code maintenance,
>> code review of SIMD contributions from others,
>> performance-related features,
>> sharing SIMD and C++ expertise with the team and growing a NumPy 
>> sub-team around it,
>> SIMD build system migration to Meson,
>> and wherever else Sayed’s interests take him.
>>
>> “I’m both happy and nervous: this is a great opportunity, but also a 
>> great responsibility,” said Sayed in response to his appointment.
>>
>> The funds for the NumPy Fellowship Program come from a partnership with 
>> Tidelift and from individual donations. We sincerely thank both Tidelift and 
>> everyone who donated to the project—without you, this program would not be 
>> possible! We also acknowledge the CPython Developer-in-Residence and the 
>> Django Fellowship programs, which served as inspiration for this program.
>>
>> Sayed officially starts as the NumPy Dev