Update to use Pyrax #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Migrate Cloudfiles exception handling to handle Pyrax exceptions.
Refine comments and remove commented-out code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently had a need to migrate some files from Rackspace to Amazon S3 and found this repo, but it wouldn't work with a Cloud Files container in the
DFWregion, so I updated it to usepyraxinstead ofpython-cloudfiles. I mostly worked on converting thepython-cloudfilesfunction calls topyrax, and updatingrequirements.txtwith some other minor changes for debugging. It worked for me, so I'm contributing it to your repo.p.s. please consider merging in the original README from the other PR. Thank you!