Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Add address_sorting to PYTHON-MANIFEST | Mehrdad Afshari | 2018-04-09 |
| | |||
* | Changes | Ken Payson | 2017-04-13 |
| | |||
* | Switch to Makefile based build on mac | Ken Payson | 2017-04-13 |
| | |||
* | Merge remote-tracking branch 'upstream/master' into cares_buildin | Yuchen Zeng | 2016-08-24 |
|\ | |||
| * | Add Python3.5 artifact targets | Ken Payson | 2016-08-15 |
| | | |||
* | | Fix python build | Yuchen Zeng | 2016-08-11 |
|/ | |||
* | Fix missing source file | Masood Malekghassemi | 2016-07-13 |
| | |||
* | Make Python build standalone on Windows | Masood Malekghassemi | 2016-07-08 |
| | |||
* | Make running individual Python tests less painful | Masood Malekghassemi | 2016-07-01 |
| | | | | | | | | | | | | | | | | | | | | | | | | Before this change, running Python tests individually required building a tox environment via the run_tests script and then specifying long environment variables to filter out just the test we wanted to run (and then we wouldn't be able to get the output on interrupt, nor would we have an easy way of determining the PID of the process for debugger attachment). Now invoking the build_python.sh script creates a workable python virtual environment that includes all necessary libraries and tests (s.t. running a single test is now possible by just knowing the module name). This does not change existing supported means of running tests (e.g. through run_tests.py). An additional way of running individual tests has been introduced. Following invocation of `./tools/run_tests/build_python.sh` (or run_tests.py), one may invoke ./$VENV/bin/python -m $TEST_MODULE_NAME and acquire a single running process that *is* the test process (rather than a parent of the process). $VENV is the virtual environment name specified to `build_python.sh` (defaults to `py27`) and $TEST_MODULE_NAME is what it says on the tin. | ||
* | Add egg-info to python distribution. | Ken Payson | 2016-06-21 |
| | | | | | | | | Currently, grpcio cannot be used as a dependency for egg packages (https://github.com/grpc/grpc/issues/6939) There is likely a better solution, but this is intended as a patch for the 0.15.0 release. | ||
* | Add missing dependencies | Masood Malekghassemi | 2016-03-29 |
| | |||
* | Exclude cygrpc.so from the Python package | Masood Malekghassemi | 2016-02-18 |
| | |||
* | Use precompiled extensions only | Masood Malekghassemi | 2016-02-12 |
| | |||
* | Add grpc_version.py to PYTHON-MANIFEST.in | Masood Malekghassemi | 2016-02-09 |
| | |||
* | Merge pull request #4821 from soltanmm/install-doctor | Masood Malekghassemi | 2016-01-25 |
|\ | | | | | Add compiler error diagnostics to Python setup | ||
* | | Integrate zlib into Python distribution | Masood Malekghassemi | 2016-01-22 |
| | | |||
| * | Add compiler error diagnostics to Python setup | Masood Malekghassemi | 2016-01-22 |
|/ | |||
* | Use BoringSSL for Python gRPC | Masood Malekghassemi | 2016-01-11 |
| | |||
* | Use default gRPC roots.pem if none provided | Masood Malekghassemi | 2016-01-11 |
| | |||
* | Redirect Python manifest to less ambiguous filename | Masood Malekghassemi | 2016-01-07 |