[Python-ideas] Please reconsider the Boolean evaluation of midnight

[Amber Yust]

I think this is the wrong stage to evaluate cost. After all, one of the
tenets of open source is that the core devs don't have to be the source of
all change.

I see a difference between "this could be better, but the core devs aren't
going to spend time on it" and "this should not change."

It would be nice if those two were not conflated so much.
On Mar 5, 2014 9:58 AM, "Paul Moore" <p.f.moore at gmail.com> wrote:

> On 5 March 2014 17:27, Amber Yust <amber.yust at gmail.com> wrote:
> > Let's turn this around. Aside from backwards compatibility, what benefit
> is
> > there from having midnight evaluate as false?
>
> Zero cost. Any alternative must justify the cost of making the change.
> Simple as that. Quantify the cost of making the change (properly!) and
> describe the benefits in such a way as to justify those costs.
>
> Paul
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20140305/9ecbb54b/attachment.html>