-
Notifications
You must be signed in to change notification settings - Fork 19
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
[PyPI] platform_system parsing problem #146
Comments
FYI, this does indeed look like an invalid version specification to me. Did the command successfully install? It would be great if the error message included the parent, i.e. the package which had the requirement with the invalid specifier. |
The installation looks good to me:
|
This looks like a parser error to me, the line is
see https://github.com/ipython/ipykernel/blob/main/pyproject.toml#L34C6-L34C13
Updated the issue title to reflect the real problem. |
The issue is not reproducible on macOS, so I'm guessing parsing of |
Sorry, still don't really understand, is this a valid specification?
specifically the |
I downloaded https://files.pythonhosted.org/packages/b0/71/348c659f0fbbf526ca77fae9fd31d43a3c90d4d60ae3df6d477055ee90d5/ipykernel-6.28.0-py3-none-any.whl and unpacked it.
but if you install with pixi,
so there is no
|
This error comes from a previous ipykernel version (ipython/ipykernel#709) I think we could do a better job at reporting the error (add the version it comes from). I believe pip (and we) just skip over packages with wrong metadata. Not sure if we should show this to the user by default (since they can't change it usually). |
Yeah this is correct, both @baszalmstra and took that behavior from pip. |
@wolfv Thank you! I guess we can just do an s/ERROR/Warning/ since it was quite confusing as it did install the package. |
Yeah, that part does seem a bit strange to me, as it explicitly skips the requirement if it can't parse: So I'm guessing the dependency still comes in somewhere down the line? |
Ah, after talking to @wolfv I understand that it is a problem during backtracking, so not really for the package it selected in the end. I think we could make the log a Warning or Debug statement for now. :) |
Reproducer on linux-aarch64:
pixi.toml
pixi install
results in:The text was updated successfully, but these errors were encountered: