-
Notifications
You must be signed in to change notification settings - Fork 13
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 python-magic-bin seems to be unmaintained #95
Comments
👋 Hey @satya-waylit Thanks for the report, I've looked into it a bit and looks like we install Ultimately, it looks like when this PR gets merged, we'll be able to remove our dependency on But until then, I'm not sure if there is an easy resolution. Are you able to run with WSL as opposed to with windows directly? |
@wilhelmklopp Indeed, using Windows. I was using WSL for the longest, but WSL seems to getting very unstable these days. May be that's why I ran into this issue. Will wait for the upstream fix. |
I checked mocket's code and it seems magic should be an optional dependency. mindflayer/python-mocket#254 |
I see that kolo specifies My PR on python-magic builds The error in the issue description implies that the user is on platform_system Windows, but no wheels available for his distribution according to uv. Maybe ARM64 Windows? In that case, my PR won't solve OP's issue. |
amd64 in my case |
then you should be covered 🤔 can you post the output here of the following direct reference install of python-magic-bin?
|
and also the output of
|
@wilhelmklopp The mocket author has switch to puremagic from python-magic in the newest version. Hopefully that'll solve the problem. |
python-magic-bin dropped as a dependency in kolo as of v2.33.9 – nice work on getting this in front of the right people @satya-waylit |
I ran into an error trying to resolve
kolo
usinguv
. I'm using Python 3.12. Seemspython-magic-bin
hasn't seen an update since 2017. The packagepython-magic
seems to be maintained. Any chance to switch to a maintained dependency?The text was updated successfully, but these errors were encountered: