What steps will reproduce the problem? 1. Try to acquire lock with timeout = 0

What is the expected output? What do you see instead? Timeout=0 should behave the same as timeout=0.0001 or whatever. Instead, it treats timeout=0 as timeout=None, thus disabling the feature.

I submitted a pull request for this.

I already fixed this, just hasn't been pushed yet.