Hi! N.angle(z) returns nan if either z.real or z.imag is nan; presently, this is not documented in its docstring, but it is traceable to the low-level c functions N.angle uses to do its work, so I'm assuming it's a bug in the doc, not in the code, i.e., is intended behavior, correct? DG
On Wed, Mar 3, 2010 at 02:28, David Goldsmith <d.l.goldsmith@gmail.com> wrote:
Hi! N.angle(z) returns nan if either z.real or z.imag is nan; presently, this is not documented in its docstring, but it is traceable to the low-level c functions N.angle uses to do its work, so I'm assuming it's a bug in the doc, not in the code, i.e., is intended behavior, correct?
It is intended behavior. I'm not sure it *needs* to be documented or that it's a doc bug that it isn't explicitly mentioned. If we were explicit about every time an input containing a NaN generates a NaN in the output, we would document nothing else. I would think this behavior is obvious once you know how NaNs usually work. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Wed, Mar 3, 2010 at 7:43 AM, Robert Kern <robert.kern@gmail.com> wrote:
On Wed, Mar 3, 2010 at 02:28, David Goldsmith <d.l.goldsmith@gmail.com> wrote:
Hi! N.angle(z) returns nan if either z.real or z.imag is nan; presently, this is not documented in its docstring, but it is traceable to the low-level c functions N.angle uses to do its work, so I'm assuming it's a bug in the doc, not in the code, i.e., is intended behavior, correct?
It is intended behavior. I'm not sure it *needs* to be documented or that it's a doc bug that it isn't explicitly mentioned. If we were explicit about every time an input containing a NaN generates a NaN in the output, we would document nothing else. I would think this behavior is obvious once you know how NaNs usually work.
I thought you would say something like that. DG
-- Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On Wed, Mar 3, 2010 at 10:39, David Goldsmith <d.l.goldsmith@gmail.com> wrote:
On Wed, Mar 3, 2010 at 7:43 AM, Robert Kern <robert.kern@gmail.com> wrote:
On Wed, Mar 3, 2010 at 02:28, David Goldsmith <d.l.goldsmith@gmail.com> wrote:
Hi! N.angle(z) returns nan if either z.real or z.imag is nan; presently, this is not documented in its docstring, but it is traceable to the low-level c functions N.angle uses to do its work, so I'm assuming it's a bug in the doc, not in the code, i.e., is intended behavior, correct?
It is intended behavior. I'm not sure it *needs* to be documented or that it's a doc bug that it isn't explicitly mentioned. If we were explicit about every time an input containing a NaN generates a NaN in the output, we would document nothing else. I would think this behavior is obvious once you know how NaNs usually work.
I thought you would say something like that.
I long for the day when I can be replaced by a machine that will predict the appropriate curmudgeonly response I would give. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
participants (3)
-
David Goldsmith -
Keith Goodman -
Robert Kern