Thanks Udi! This is the issue. I'm trying to upgrade from 2.18 where build-requirements.txt didn't exist.
Is there a reason why this cannot happen automatically when running python3.6 setup.py sdist bdist_wheel ? Thomas On Thu, May 7, 2020 at 11:07 AM Udi Meiri <eh...@google.com> wrote: > Probably not the issue, but double checking: are you running "pip install > -r sdks/python/build-requirements.txt" first? > > On Wed, May 6, 2020 at 7:22 PM Thomas Weise <t...@apache.org> wrote: > >> I'm working on rebasing our fork to 2.21.0 and run into a problem >> installing grpcio-tools that leads to *ModuleNotFoundError: No module >> named 'grpc_tools' *(see details below) >> >> I cannot reproduce this locally. >> >> Any =suggestions on what to look for? >> >> Thanks, >> Thomas >> >> [?25hBuilding wheels for collected packages: future, gr >> Running setup.py bdist_wheel for future ... [?25l- \ >> [?25h Stored in directory: >> /root/.cache/pip/wheels/bf/c9/a3/c538d90ef17cf7823fa51fc701a7a7a910a80f6a405bf1 >> Running setup.py bdist_wheel for grpcio ... [?25l- \ | / - \ | / - \ | >> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - >> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | >> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - >> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | >> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - >> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | >> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - >> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | >> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - >> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | >> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - >> \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | >> / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - >> \ | / - \ | / - \ | >> [?25h Stored in directory: >> /root/.cache/pip/wheels/00/4d/5f/07d0d4283911d2b917b867a11b1622d9d2cc8c286eefd1 >> Successfully built future grpcio >> Installing collected packages: six, grpcio, setuptools, protobuf, >> grpcio-tools, future, mypy-protobuf >> Successfully installed future-0.16.0 grpcio-1.28.1 grpcio-tools-1.14.2 >> mypy-protobuf-1.18 protobuf-3.11.3 setuptools-46.1.3 six-1.14.0 >> WARNING:root:Installing grpcio-tools took 305.39 seconds. >> INFO:gen_protos:Regenerating Python proto definitions (no output files). >> Process Process-1: >> Traceback (most recent call last): >> File >> "/src/streamingplatform/beam-release/beam/sdks/python/gen_protos.py", line >> 292, in generate_proto_files >> from grpc_tools import protoc >> ModuleNotFoundError: No module named 'grpc_tools' >> >> On Fri, Apr 10, 2020 at 10:01 AM Kyle Weaver <kcwea...@google.com> wrote: >> >>> Hi everyone, >>> >>> Just a heads up that the Beam 2.21 release branch [1] is cut. >>> - If you find any important issues that you think should be addressed in >>> the release, please tag the jira with fix version 2.21.0 and cc me >>> (username `ibzib`). >>> - Make sure to update the change log [2] with any significant changes if >>> you haven't already. Send a PR with the change and tag me. (I imagine I'm >>> not the only one who forgot to do this :).) >>> >>> Thanks, >>> Kyle >>> >>> [1] https://github.com/apache/beam/blob/release-2.21.0 >>> [2] https://github.com/apache/beam/blob/master/CHANGES.md >>> >>
