Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move proto to within weaviate to avoid collisions #592

Merged
merged 1 commit into from
Oct 31, 2023

Conversation

tsmith023
Copy link
Collaborator

This PR fixes an issue raised in #591 whereby the naming convention of this package created a collision with Google's proto-plus package, which already holds the proto namespace

@weaviate-git-bot
Copy link

Great to see you again! Thanks for the contribution.

beep boop - the Weaviate bot 👋🤖

PS:
Are you already a member of the Weaviate Slack channel?

@tsmith023 tsmith023 merged commit 6ce06cc into main Oct 31, 2023
@tsmith023 tsmith023 deleted the fix/naming-collision-with-google-proto-package branch October 31, 2023 10:30
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.

New module proto (since 3.25) conflicting with Google's protobuf package that also has a proto module
3 participants