What do you mean by "changing the API"?
- Case (A): Adding a property `P.coef_natural` is not a change IMO, it is an
addition.
- Case (B): Do you consider that changing `P.coef` from an attribute to a
property is a change in the API ? It is transparent IMO.
___
On Sun, Sep 1, 2024 at 6:48 AM Rakshit Singh
wrote:
> Best Wishes
>
> I am really hesitant of changing the api, some packages might be dependent
> on it.
>
> Regards
> Rakshit Kr. Singh
>
> On Sun, Sep 1, 2024, 5:54 PM oc-spam66--- via NumPy-Discussion <
> numpy-discussion@python.org> wrote:
>
>>
Best Wishes
I am really hesitant of changing the api, some packages might be dependent
on it.
Regards
Rakshit Kr. Singh
On Sun, Sep 1, 2024, 5:54 PM oc-spam66--- via NumPy-Discussion <
numpy-discussion@python.org> wrote:
> I can summarize the different possibilities/proposals:
> (A) Create new
I can summarize the different possibilities/proposals:
(A) Create new properties: add a `P.coef_natural` property, with a suitable
documentation ; maybe also add a `P.coef_internal` property. There would be no
change to the existing code (only addition of properties).
(B) Change `P.coef` attribut
Hi Olivier,
Thanks for bringing this up here! As stated by Chuck in the issue
leading to the PR,
https://github.com/numpy/numpy/issues/26401
there are real risks with using natural coefficients for polynomials:
we really want to move people away from situations in which large
cancellation error
