This repository has been archived by the owner on Sep 14, 2020. It is now read-only.
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.
Switch to pykube-ng to handle arbitrary resources (pods, jobs, etc) #110
Switch to pykube-ng to handle arbitrary resources (pods, jobs, etc) #110
Changes from all commits
e53a598
6331c1a
490a4d3
05a3088
41e1ff6
1a7faef
0f021c7
d225cfa
27da45c
1e2b806
44602c1
2118b8e
0db1078
495744b
f75fa7a
f105def
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the
rsp.raise_for_status()
can be removed, becauseapi.raise_for_status(rsp)
already does it and you are already catching everything.Basically if the first line raises, the second would as well (but will not be run because the first raised), and if the first line doesn't raise, then the second won't either, so nothing is gained by having both.