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
Hello,
I would like to add a property `P.coef_natural` to polynomials. Would you
accept it?
Reason:
Most people who had ground courses on polynomials expect `P.coef` to return the
natural coefficients. They face a huge confusion because this is not the case
and because the `coef` attribute is n
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.
___
Hello,
I discovered the horror below. Do we really want silent data type casting in
this case?
from numpy import *
x = array([0])
x[0] = 1.7# Silent data type casting
print(x)# Prints [1] instead of [1.7]
Olivier
___
NumPy-Discussion maili
