-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
app_paths dependency is a nuisance #64
Comments
Filed a request as alexdelorenzo/app_paths#3. |
Reported issues:
I checked on the "old appdirs" and that appears not to be an issue:
Where did you get the impression that it depends on an old appdirs? |
Can you elaborate a bit on what an NIH package is and which dependencies are (most) concerning? I could guess, but I'd like to understand your perspective better. I do agree, at least for my usage, a thin wrapper around appdirs with fewer dependencies would be nice. |
I'm sorry for not being precise. I meant it is using
In my case, it means having to package On top of that, we already have |
Please feel free not to invest the time/energy into packaging those downstream dependencies until this issue is resolved. I agree that a likely outcome should be to reduce the dependency tree here. |
Looks like |
Thanks a lot! |
Per 3463926#r94301964, @mgorny reports that the app_paths dependency is problemmatic. Let's explore ways to fix that.
The text was updated successfully, but these errors were encountered: