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

Bugfix: don't rely on $HOME to be set #311

Merged
merged 1 commit into from Apr 11, 2014

Conversation

Projects
None yet
2 participants
@alertedsnake
Copy link
Contributor

alertedsnake commented Apr 10, 2014

Makes a decent assumption about default platform and pick .s3cfg location using os.path.expanduser, rather than relying on $HOME to be set. In the case where a config file is not required (such as command-line AWS key arguments or a EC2 instance role), not having $HOME set would erroneously cause an error.

Bugfix: make a decent assumption about default platform and pick .s3cfg
location using os.path.expanduser, rather than relying on $HOME to be set.

mdomsch added a commit that referenced this pull request Apr 11, 2014

@mdomsch mdomsch merged commit 1767a9a into s3tools:master Apr 11, 2014

@mdomsch

This comment has been minimized.

Copy link
Contributor

mdomsch commented Apr 11, 2014

merged, thanks!

@alertedsnake alertedsnake deleted the alertedsnake:bugfix_default_cfgfile_path branch Apr 11, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.