-
Notifications
You must be signed in to change notification settings - Fork 262
Virtualenv 20.31.0 breaks cibuildwheel testing #2380
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
Comments
I assume (hope) you hit this due to |
That seems to be the case: |
We do need to remove |
Yea, no clue where that's coming from. Maybe the Anyhow, |
I expect a package you are using has this in it somewhere, it's easy to hit it, for example older Poetry runs into this (and Poetry recommends capping 🤣). We should conditionally remove the |
we're still using cibuildwheel/cibuildwheel/linux.py Lines 364 to 366 in faf86a6
|
Seems like the virtualenv v20.31.2 release fixed this. And with https://github.com/jeremyleung521/westpa/actions/runs/14843629528/job/42069809562#step:4:383 |
Description
I was in a unique position where my CI (https://github.com/westpa/westpa/actions/runs/14840584129/attempts/1) ran slightly before and after the release of
virtualenv
20.31.0.From my investigation, it seems like
virtualenv
v20.31.0 no longer bundles/supportswheel
directly and that leads tovirtualenv: error: unrecognized arguments: --wheel=embed
during testing, where it would somehow pull the newest virtualenv version (?). This suggests that there needs to be some changes in cibuildwheel workflow.EDIT: Seems like related to this: #2329
Build log
https://github.com/westpa/westpa/actions/runs/14840584129/job/41665220582#step:4:288
CI config
https://github.com/westpa/westpa/actions/runs/14840584129/workflow
The text was updated successfully, but these errors were encountered: