Skip to content

Conversation

@tisonkun
Copy link
Member

Signed-off-by: tison <wander4096@gmail.com>
'pytz',
'futures>=3.2.0;python_version<"3.2"',
'grpcio<1.28,>=1.8.2',
'grpcio>=1.37',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that we have to put a cap here otherwise auto upgrades may break the client.
IIRC it happened in the past.

I I am mot sure that we have CI that is covering this change.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! I threw the change here to see if it breaks anything. To prepare a solid patch I need more time to understand the mechanism and see how to verify the change.

@tisonkun
Copy link
Member Author

Closed for now.

@tisonkun tisonkun closed this Aug 19, 2022
@merlimat
Copy link
Contributor

@tisonkun I think we should re-open this, and move to newer Grpc. Otherwise the Pulsar Python client is still stuck with unsupported Grpc version

@merlimat
Copy link
Contributor

My bad, this was already addressed in #3875

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants