Skip to content

Conversation

jeffwidman
Copy link
Contributor

In Python3, ConnectionError is a native exception. So rename our custom one to KafkaConnectionError to prevent accidentally shadowing the native one.

Note that there are still valid uses of ConnectionError in this code.
They already expect a native Python3 ConnectionError, and also already
handle the Python2 compatibility issues.

In Python3, `ConnectionError` is a native exception. So rename our
custom one to `KafkaConnectionError` to prevent accidentally
shadowing the native one.

Note that there are still valid uses of `ConnectionError` in this code.
They already expect a native Python3 `ConnectionError`, and also already
handle the Python2 compatibility issues.
@jeffwidman jeffwidman force-pushed the Stop-shadowing-native-python-ConnectionError-exception branch from ea3f2b8 to c9fba20 Compare May 10, 2018 23:15
@jeffwidman
Copy link
Contributor Author

Note that this is a breaking change for anyone who did from kafka.errors import ConnectionError.

@jeffwidman
Copy link
Contributor Author

@tvoinarovskyi / @dpkp can one of you review? I don't trust the test suite is executing all these code paths...

@jeffwidman jeffwidman requested a review from dpkp May 23, 2018 22:17
@jeffwidman jeffwidman merged commit 11cf397 into master May 23, 2018
@jeffwidman jeffwidman deleted the Stop-shadowing-native-python-ConnectionError-exception branch May 23, 2018 22:19
@tvoinarovskyi
Copy link
Collaborator

Sorry for being so late, it's a good PR. 1 moment thou, we don't want to break existing code, so we should make an alias for ConnectionError in errors.py

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.

2 participants