Use the all to install the py3-grpcio, and then use the requirements.txt to
install the pulsar-client, it works fine.
This is a workaround.
Thanks,
Zixuan
Yunze Xu 于2024年5月15日 周三10:51写道：
> > I tried but it didn't work.
>
> Could you share the CI workflow so I can take a look? Meanwhile, would
> I tried but it didn't work.
Could you share the CI workflow so I can take a look? Meanwhile, would
you like to start the release for Python client 3.5.1?
Thanks,
Yunze
On Sat, May 11, 2024 at 5:54 PM Zixuan Liu wrote:
>
> > Please release 3.5.1 rather than 3.4.1 because 3.5.0 is already
> rel
> Please release 3.5.1 rather than 3.4.1 because 3.5.0 is already
released. It's too heavy to maintain old releases for client libraries
for now.
Let's go to 3.5.1.
> However, it would be better to remove the `functions` component from
pulsar-client-python because the Python client itself never u
Sorry I missed the discussion link:
https://lists.apache.org/thread/5s2l9vgt5f973psb6xlttpmy4rpym7zh
Would this release block the Pulsar 3.3.0 release? If yes, a quicker
way to fix it was to add a `requirements.txt` that includes a proper
version of grpcio and then run `python -m pip install -r
py
Please release 3.5.1 rather than 3.4.1 because 3.5.0 is already
released. It's too heavy to maintain old releases for client libraries
for now.
However, it would be better to remove the `functions` component from
pulsar-client-python because the Python client itself never uses these
dependencies.
Hi all,
https://github.com/apache/pulsar-client-python/pull/174 breaks the
python-client installation in the pulsar arm image, and then the release
manager of pulsar@3.3.0 will take about 2 hours to build the grpcio wheel,
please see
https://github.com/nodece/pulsar-python-deps-build/actions/runs/
