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

[Mark Lawrence]

On 05/03/2014 19:18, Shai Berger wrote:
> On Wednesday 05 March 2014 20:47:02 Mark Lawrence wrote:
>> On 05/03/2014 18:33, Shai Berger wrote:
>>> On Wednesday 05 March 2014 20:23:12 Mark Lawrence wrote:
>>>> On 05/03/2014 18:12, Amber Yust wrote:
>>>>> 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.
>>>>
>>>> But the core devs have to review the change and ultimately decide
>>>> whether or not to commit it.  In this case it looks as if a patch would
>>>> not be accepted, so why keep going on about it, especially when there's
>>>> a known work around?
>>>
>>> As noted before, the workaround is trivial once you detect the problem.
>>> Detecting the problem is not easy.
>>>
>>> Shai.
>>
>> Use mocks in unit testing?
>
> Unless you're aware of the issue, you are not going to unit-test specifically
> for midnight. If you are aware, you don't need to detect it, you write "is not
> None".

So you have your solution.  Good, now can we please move on as this is 
getting tedious.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com