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

Dependency Conflict with Protobuf Version Requirement in sillm-mlx #9

Closed
GusLovesMath opened this issue May 4, 2024 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@GusLovesMath
Copy link

Description
I am encountering a dependency conflict when trying to install sillm-mlx v0.1.3 in a new conda virtual environment. The library requires protobuf>=5.26.1, but my setup includes protobuf v4.25.3, which conflicts with other packages that depend on an older version of protobuf.

Steps to Reproduce

  1. Create a new conda virtual environment.
  2. Install sillm-mlx v0.1.3 using pip.
  3. Observe the dependency resolution failure when installing requirements.txt.

Behavior
The pip installation process terminates with an error, highlighting a dependency conflict due to the required version of protobuf by sillm-mlx, which is incompatible with other installed packages.

Environment Details

  • Python Version: 3.11 and tried 3.10
  • Operating System: macOS Sonoma on a Mac 2022 M2 Pro chip
  • Conda Environment

I would appreciate any advice on resolving this issue, including potential updates to the package's dependency specifications to accommodate a broader range of protobuf versions or guidance on managing dependencies more effectively in this scenario.

Thank you! :D

@armbues
Copy link
Owner

armbues commented May 5, 2024

Thank you for pointing this out!

This conflict exists, but actually not in a fresh conda env as described. It is triggered when you install chainlit which requires protobuf 4.25.3. This does not cause any issues with sillm-mlx that I'm aware of though. I will remove the requirement for sillm in the next release. Until then you can just use it and ignore the error thrown by pip.

@GusLovesMath
Copy link
Author

Sounds good! Thank you so much!!!

@armbues armbues added the bug Something isn't working label May 7, 2024
@armbues armbues closed this as completed Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants