grpc - RPC system from Google

	Commit message (Collapse)	Author	Age
*	Support gRPC Python client-side fork with epoll1	Eric Gribkoff	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	Mehrdad Afshari	2018-06-08
\|
*	Disable additional pylint warnings due to upgrade	Mehrdad Afshari	2018-06-07
\|
*	Eliminate broad-except suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate bare-except suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate old-style-class suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate wildcard-import suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate function-redefined suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate unnecessary-lambda suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate undefined-variable suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate non-iterator-returned suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate undefined-loop-variable suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate raising-bad-type suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate unreachable suppression	Mehrdad Afshari	2018-04-19
\|
*	Eliminate bad-continuation suppression	Mehrdad Afshari	2018-04-19
\|
*	Run pylint on Python test code	Mehrdad Afshari	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.