-
Notifications
You must be signed in to change notification settings - Fork 283
Make the {project}
placeholder available to repair-wheel-command
#2589
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
base: main
Are you sure you want to change the base?
Make the {project}
placeholder available to repair-wheel-command
#2589
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @arcondello! This looks good to me. Could you also mark #1931 to be closed with this?
Oh wow, totally missed that one. Updated |
I'm a little surprised we don't run the command from the project directory on Linux. |
This is what's confusing me also... I'm 90% sure that we do...! But I think this can still be useful so I'm happy to merge it. On testing, it appears that the previous test did actually assert that the cwd was the project directory previously. Could we make sure that we don't lose that too? It might be best to revert the test change and add another test, perhaps on just a single python version, that runs the script with the |
Sure, I can do that |
As an alternative, if the intent is always to run the |
Yes, that is the intention. I doubt that will change - the other commands like before-build etc. also run from the project dir (which is the cwd when cibuildwheel starts). Logic with relative paths gets pretty strange if we change this rule! Happy to see this noted in the docs. Also, I think it might be nice for consistency for |
Closes #2588
Closes #1931
Let me know if you'd prefer a different approach for testing, the change I made amounts to a smoke test.