-
Notifications
You must be signed in to change notification settings - Fork 60
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
No more Windows support since 48e781 #66
Comments
* GaryO <[email protected]> wrote:
I've been using this for some years on Windows, Mac and Linux to
manage my dotfiles, and just recently updated to latest version. I
notice you removed Windows symlink support in 48e781, which I added a
very long time ago. Just wondering if that was intentional.
Sorry about that, I was thinking that python3 resolved this and that
compatibility code was no longer necessary, but I could certainly be
wrong about that. It was not intentional to cause a regression. I'll
try to post an update soon, within the week hopefully.
…--
Jon
|
Some time ago I switched to pylib, which simplified the code substantially and I thought windows was supported as well. It's in maintenance mode now and python's pathlib appears to be the standard over os.path - and has nearly a one-to-one mapping of methods from pylib. There's a compatibility module pathlib2 for pre python 3.4 which should allow the functionality to be realized by any supported version of python (including 2.7). So my plan is to migrate to pathlib. Do you see any problems with this approach? Does pathlib work reliably on your platform in general? |
It should - I’m only using one package (click) for the CLI, everything else is in the standard library. Specifically pathlib which claims to support Windows without issue, though how true remains untested in this context. Either way, if there are issues on Windows I will try to fix them, I do care about that platform and I consider failures there to be a bug. |
I've been using this for some years on Windows, Mac and Linux to manage my dotfiles, and just recently updated to latest version. I notice you removed Windows symlink support in 48e781, which I added a very long time ago. Just wondering if that was intentional.
The text was updated successfully, but these errors were encountered: