ACTIVITY SUMMARY (2013-08-09 - 2013-08-16)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4152 ( +4)
closed 26377 (+56)
total 30529 (+60)
Open issues wit
On Aug 16, 2013 11:05 AM, "Steven D'Aprano"
wrote:
>
> I'll provide two functions: mode, which returns the single value with the
highest frequency, or raises; and a second function, which collates the
data into a sorted (value, frequency) list. Bike-shedding on the name of
this second function is
On 16/08/13 17:47, Oscar Benjamin wrote:
I can't think of a situation where 1 or 2 modes are acceptable but 3
is not. The only forms I can imagine using are mode(data) to get the
unique mode if it exists and mode(data, max_modes=None) to get the set
of all modes.
Hmmm, I think you are right. Th
On 15/08/13 14:08, Steven D'Aprano wrote:
On 15/08/13 21:42, Mark Dickinson wrote:
The PEP and code look generally good to me.
I think the API for median and its variants deserves some wider discussion:
the reference implementation has a callable 'median', and variant callables
'median.low',
On Fri, 16 Aug 2013 12:44:54 +1000
Steven D'Aprano wrote:
> On 16/08/13 04:10, Eric V. Smith wrote:
>
> > I agree with Mark: the proposed median, median.low, etc., doesn't feel
> > right. Is there any example of doing this in the stdlib?
>
> The most obvious case is datetime: we have datetime()
On 15 August 2013 14:08, Steven D'Aprano wrote:
>
> - The API doesn't really feel very Pythonic to me. For example, we write:
>
> mystring.rjust(width)
> dict.items()
>
> rather than mystring.justify(width, "right") or dict.iterate("items"). So I
> think individual methods is a better API, and one
