Skip to content
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

Add support for XDG_CONFIG_HOME #235

Merged
merged 2 commits into from
May 7, 2021

Conversation

mpnowacki-reef
Copy link
Collaborator

replaces #129

@mpnowacki-reef mpnowacki-reef force-pushed the 0azxdg branch 2 times, most recently from a76c94c to ea785c7 Compare April 30, 2021 09:29
@mpnowacki-reef mpnowacki-reef force-pushed the 0azxdg branch 7 times, most recently from a9bcee5 to c954b49 Compare April 30, 2021 14:01
Copy link
Collaborator

@ppolewicz ppolewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's beautiful

@ppolewicz
Copy link
Collaborator

on a side note, @mpnowacki-reef shoudln't we schedule removal of everything that starts with os.path. in favor of pathlib? Maybe add that to the list of things we can do when dropping 3.5?

@mpnowacki-reef mpnowacki-reef merged commit afbe05a into Backblaze:master May 7, 2021
@mpnowacki-reef
Copy link
Collaborator Author

@ppolewicz Yes we could, but pathlib was introduced in 3.4, so i guess there's no need for it to happen only when dropping 3.5, right?

@ppolewicz ppolewicz deleted the 0azxdg branch July 17, 2021 16:28
@ppolewicz
Copy link
Collaborator

that is true, but we missed it back then, so now we track it in #239 to not forget

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants