What steps will reproduce the problem? 1. specify a pid file in a directory where you don't have write access 2. 3.

What is the expected output? What do you see instead? expect: an exception with a useful error message including the pid file path and OS error message got: an exception with no message requiring one to guess what is going on

What version of the product are you using? On what operating system? lockfile-0.9.1-py2.7

Please provide any additional information below.

Please provide error messages in all exceptions that provide enough information to understand the cause of an error without digging into the code. Including paths of lock files and what happend will save users a lot of time.

nice package!

I believe this is handled now. I had all sorts of problems transitioning from Mercurial to Git. The 0.9.1 release got caught in the crosshairs. When you can't write the pid to the pidfile it lists the path it was unable to create.