-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow InterProcessLock
to receive a pathlib.Path
object
#16
Comments
Sounds good to me as long as it will work on both py2.7 and py3.x |
I think it will since you don't even need the package, just call str(path)
|
Agreed, although probably better to call https://docs.python.org/3/library/os.html#os.fsencode if we can... |
Check and validate path types before further usage and translate pathlib objects so that they can be used correctly in further interprocess locking code. Fixes issue #16
Ok checkout #17 (I'll add some tests but seems to work locally). |
Check and validate path types before further usage and translate pathlib objects so that they can be used correctly in further interprocess locking code. Fixes issue #16
Be wary of On Mon, Dec 7, 2015 at 2:48 AM, Joshua Harlow notifications@github.com
|
Hmmm, why u bundling it 😦 I get that concern, but it seems like a 1% case (and not especially a 1% case that I like, bundling stuff IMHO is ummm not helping the python ecosystem in general, although I get the reasons why people do it, I just don't agree with them, ha). |
Also consider there are alternatives to Pathlib which act similarly but Sent from my phone.
|
Fair enough, maybe should just do str() as u said... |
Check and validate path types before further usage and translate pathlib objects so that they can be used correctly in further interprocess locking code. Fixes issue #16
Convert/normalize path types before further usage and attempt to translate non-string objects so that they can be used correctly in further interprocess locking code. Fixes issue #16
No description provided.
The text was updated successfully, but these errors were encountered: