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
packaging==22.0 breaks aiidalab install #339
Comments
Hmm, maybe EDIT: Nope, it's definitely |
Should we switch to flit? Happy to open a PR for that. [UPDATE] |
Not sure what you mean? The issue here is not with the build.
Dne st 14. 12. 2022 8:00 dop. uživatel Aliaksandr Yakutovich <
***@***.***> napsal:
… Should we switch to flit?
—
Reply to this email directly, view it on GitHub
<#339 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIY64IW3JBWISJDH67HGHDWNF5DRANCNFSM6AAAAAAS52DFW4>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Yeah, I realised that later 😅 . That is why I wrote an update:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
I will re-open this so that we remember to fix this properly (for now we only pinned to the old version of |
I think this the same issue as in aiidalab/aiidalab-registry#103 |
Package
packaging
version 22.0 breaks theaiidalab install
command. Here's what I seeDowngrading to version 21.3 fixes the issue. We need to either constrain the version in
setup.cfg
or fix the underlying issue.Note, in the current docker-stack this is not an issue since
packaging
is already installed in the underlying jupyter image. But as soon as they update we will break.The text was updated successfully, but these errors were encountered: