➜

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 oscarbenjamin
Recipients gregory.p.smith, larry, ncoghlan, oscarbenjamin, python-dev, steven.daprano, wolma
Date 2014-02-08.15:56:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAHVvXxTucGbRnPr2=k7UKVRvfW85w_gJSPM9E=KT7rUfkBo_6g@mail.gmail.com>
In-reply-to <3fLq3h1b56z7LjN@mail.python.org>
Content 
> Close #20481: Disallow mixed type input in statistics

If I understand correctly the reason for hastily pushing this patch
through is that it's the safe option: disallow mixing types as a quick
fix for soon to be released 3.4. If we want to allow mixing types then
that can be a new feature for 3.5.

Is that correct?

If so should the discussion about what to do in 3.5 take place in this
issue (i.e. reopen for 3.5) or should it be a new issue? issue20499
would benefit from clarity about the statistics module policy for
mixing types.
History
Date User Action Args
2014-02-08 15:56:05oscarbenjaminsetrecipients: + oscarbenjamin, gregory.p.smith, ncoghlan, larry, steven.daprano, python-dev, wolma
2014-02-08 15:56:05oscarbenjaminlinkissue20481 messages
2014-02-08 15:56:05oscarbenjamincreate