-
Notifications
You must be signed in to change notification settings - Fork 50
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
update python/lua KVS bindings to not use kvs classic functions #1748
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1748 +/- ##
==========================================
- Coverage 79.62% 79.59% -0.04%
==========================================
Files 185 185
Lines 34451 34459 +8
==========================================
- Hits 27433 27426 -7
- Misses 7018 7033 +15
|
it appears the trivial cleanups I did are not actually covered by any tests, thus the low diff coverage. Should I just remove the trivial cleanups? |
Looks like pylint is not happy with some of the changes.
It seems wrong to me to not include cleanups to appease the coverage tool. I'm OK with the coverage drop, but I'll defer to others on this. |
Yeah, I'm with Stevie. |
49035d1
to
95ddec3
Compare
fixed up pylint issues, already squashed patch since it was simple. Also rebased. |
LGTM |
hmmm i guess pylint conventions / warnings also have to be corrected |
95ddec3
to
8869baf
Compare
fixed warnings / convention complaints. Considered using a property decorator for |
8869baf
to
e44513e
Compare
oops, pushed the wrong tree, trying again |
Remove use of kvs_classic functions and use new KVS api functions.
Incorrect logic could return error message indicating wrong function caused error.
e44513e
to
a05e300
Compare
Maybe an ack from @SteVwonder on the python changes and then this can go in? |
Also fix random trivial things I found along the way.