➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients WarrenWeckesser, mark.dickinson, rhettinger, steven.daprano, taleinat, tim.peters
Date 2019-10-30.00:42:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572396140.59.0.565683325533.issue38382@roundup.psfhosted.org>
In-reply-to
Content 
Maybe we should hold-off on adding negative number support unless a compelling use case arises.  It is telling that scipy.stats.hmean() and that MS Excel's harmean() haven't found justification to add negative number support.

In all likelihood, a negative input is an error in the input and users would be better-off seeing an exception raised.  In a number of contexts, the negative input wouldn't make sense all:

* a 10 ohm resistor wired in parallel with a negative 5 ohm resistor
* travel 1 km at 5 kph then another 1 km at -10 kph

We really don't have to go down this route just because we can.  The usual rule is to keep the API minimal unless real use cases arise to inform the design.
History
Date User Action Args
2019-10-30 00:42:20rhettingersetrecipients: + rhettinger, tim.peters, mark.dickinson, taleinat, steven.daprano, WarrenWeckesser
2019-10-30 00:42:20rhettingersetmessageid: <1572396140.59.0.565683325533.issue38382@roundup.psfhosted.org>
2019-10-30 00:42:20rhettingerlinkissue38382 messages
2019-10-30 00:42:20rhettingercreate