-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
macOS ARM depfinder does not work on python 3.10 #40
macOS ARM depfinder does not work on python 3.10 #40
Comments
I don't have a mac to test but I was able to create a dry-run env with:
Can you test |
No idea why that doesn't work. If osx-64 is working for you then maybe this is entirely an osx-arm64 problem. |
That may be the fact that my "conda" is actually micromamba. Can you try to create and empty env with Python 3.10 and then install |
It tries to install the broken 2.7.1:
|
I get the same behavior with python 3.11. |
Okay, turns out that the conda-forge page is telling us exactly the problem: https://anaconda.org/conda-forge/depfinder ![]() noarch is only for v2.8.1. |
That's why I asked you to request "depfinder>=2.10.0" instead of just |
Yes, but it can't find something if
There is no arm mac build so it's falling back to the noarch one which is 2.8.1 as shown on the anaconda web page. |
I'm always confused about noarch on osx-arm64. We can try to add it to the migrator and see if that creates a variant for it. |
#35 seems to be asking the same question. 2.10 is not noarch but 2.8 was. |
Ideally we should issue a new depfinder version that is |
Solution to issue cannot be found in the documentation.
Issue
When I search for depfinder with python 3.10 macOS ARM I get:
If I install depfinder it gives me v2.7.1 which doesn't work:
v2.8.1 refuses to install because that one knows that stdlib-list does not work on python 3.10. It seems like a related issue is that stdlib-list is not pinned for <3.10.
v2.10 should work on python 3.10 because that uses
sys.stdlib_module_names
but is not available to me. I don't know if that is macOS-specific or a general feedstock problem.Installed packages
Environment info
The text was updated successfully, but these errors were encountered: