It's always true because the func is always a real, truthy func object. In the cmake case, the logic seems to be broken because if a path is not a file, then that includes the case where it does not exist. It also clearly meant "or" instead of "and". What actually ended up happening was that this check never fired at all. Because "if not func and not ..." would always fail, because "not func" is always false. Maybe we don't need this logic at all...pull/13483/head
parent
433c13c5c4
commit
f2de6dfd10
2 changed files with 2 additions and 2 deletions
Loading…
Reference in new issue