Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Add ignore to .pylintrc-tests | 2018-12-11 | |
| | |||
* | Remove the ignore-pattern in .pylintrc-tests | 2018-12-11 | |
| | |||
* | Upgrade sanity Docker image to debian:stretch | 2018-12-10 | |
| | | | | | | | | * Use latest pylint in Python 3.7 (they dropped support for PY2) * Make latest pylint happy * Forced to upgrade to shellcheck 0.4.4 * Make shellcheck 0.4.4 happy * Adopt reviewers' advice to reduce global disabled rules | ||
* | Support gRPC Python client-side fork with epoll1 | 2018-08-22 | |
| | | | | | | | | | | | | | | | | | A process may fork after invoking grpc_init() and use gRPC in the child if and only if the child process first destroys all gRPC resources inherited from the parent process and invokes grpc_shutdown(). Subsequent to this, the child will be able to re-initialize and use gRPC. After fork, the parent process will be able to continue to use existing gRPC resources such as channels and calls without interference from the child process. To facilitate gRPC Python applications meeting the above constraints, gRPC Python will automatically destroy and shutdown all gRPC Core resources in the child's post-fork handler, including cancelling in-flight calls (see detailed design below). From the client's perspective, the child process is now free to create new channels and use gRPC. | ||
* | Change notes on suppressions | 2018-06-08 | |
| | |||
* | Disable additional pylint warnings due to upgrade | 2018-06-07 | |
| | |||
* | Eliminate broad-except suppression | 2018-04-19 | |
| | |||
* | Eliminate bare-except suppression | 2018-04-19 | |
| | |||
* | Eliminate old-style-class suppression | 2018-04-19 | |
| | |||
* | Eliminate wildcard-import suppression | 2018-04-19 | |
| | |||
* | Eliminate function-redefined suppression | 2018-04-19 | |
| | |||
* | Eliminate unnecessary-lambda suppression | 2018-04-19 | |
| | |||
* | Eliminate undefined-variable suppression | 2018-04-19 | |
| | |||
* | Eliminate non-iterator-returned suppression | 2018-04-19 | |
| | |||
* | Eliminate undefined-loop-variable suppression | 2018-04-19 | |
| | |||
* | Eliminate raising-bad-type suppression | 2018-04-19 | |
| | |||
* | Eliminate unreachable suppression | 2018-04-19 | |
| | |||
* | Eliminate bad-continuation suppression | 2018-04-19 | |
| | |||
* | Run pylint on Python test code | 2018-04-18 | |
The test modules were not under pylint jurisdiction, and actual bugs have been found in tests that would have been prevented had we run static analysis on the test code as we do on the core modules. This is the first step to enable pylint on tests. Due to numerous warnings since the code is not ready and needs refactoring, a new `.pylintrc` specific to tests is added that suppresses a number of valid warnings. The goal is stepwise elimination of each class of warning while refactoring the code such that it will not emit any warnings in future commits, always keeping the sanity checks passing and keeping the disruption minimal. |