We would love to at some point be able to build gRPC Python properly with Bazel. Last time I checked the blocker seemed to be lack of Cython support, so if you could send us a PR for to build with Bazel, we would love that! Barring that, if there's a sensible step to make the Python setup.py more adaptable to a precompiled gRPC Core, please send us a PR for that too so we can look at the change. We'll happily try to upstream if it makes sense. Thanks!
On Wednesday, April 18, 2018 at 11:39:01 AM UTC-7, [email protected] wrote: > > I was wondering if it was reasonable to have a env variable that affected > the `CORE_C_FILES` that is passed into Extension in setup.py (basically > something like SKIP_COMPILING_CORE). I’d like to build grpcio python from > source and link against grpc_core compiled separately. My understanding of > disttools is that when we pass in the gprc_core files as srcs ( > https://github.com/grpc/grpc/blob/master/setup.py#L220), it will compile > and prefer to link those, even if we make the precompiled libraries > available on library search path. > > Right now I’ve accomplished this just by editing the setup.py locally. I > think it might be useful for upstream/others as well as this allows me to > build grpc python with :grpc as a dependency that handles compiling core, > rather then recompiling it when building wheel using python setup.py > build_ext. Unfortunately I’m using some in-house bazel rules to expose a > bazel built grpcio-python that aren’t open source.. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/83edf5eb-13a8-4cda-97d5-86d59496d886%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
