* Ran `2to3` on `tools/buildgen` and the `gen_build_yaml.py` files.
* Updated the invocations of python to be explicitly Python 3.
* Changed the loader in `mako_renderer.py` to allow pickle to find the module for pickling `external_version.Version`
* Added a few open-as-binary to placate readers/writers expecting bytes.
* Hand tweaked the templates to remove `iteritems` and fiddle with encodings.
Partially addresses #24359.
- Adds a new environment variable for turning on the build of ASM
for boring SSL.
- Only enables for x86_64 for now. I think this is likely the most
common target and the only machine I have readily accessible.
All these changes need to go together to make sense
- changes to use new version of upb in bazel
- allowing includes in build target option
- script for generating c code (upb) for protos
- generated code for example protos
- adding changes for non-bazel builds
- change sanity tests to ignore the generated files.
protos
All these changes need to go together to make sense
- changes to use new version of upb in bazel
- allowing includes in build target option
- script for generating c code for protos
- generated code for example build
- adding changes for non-bazel builds
- change sanity tests to ignore the generated files.
Instead, use the same python interpreter for calling the mako renderer
that is currently use (which is sys.executable).
This is useful when trying to run generate_projects.py in a python3
only environment (which is still broken but this is a first step).
This removes all of the node code and tests from the repo, along with the
scripts for running Node unit tests, performance tests, and artifact builds.
The scripts for running tests from the grpc-node repository are untouched.