Skip to content

Conversation

arcondello
Copy link

@arcondello arcondello commented Sep 11, 2025

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.

Copy link
Member

@agriyakhetarpal agriyakhetarpal left a 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?

@arcondello
Copy link
Author

Oh wow, totally missed that one. Updated

@mhsmith mhsmith removed their request for review September 12, 2025 18:57
@henryiii
Copy link
Contributor

henryiii commented Sep 13, 2025

I'm a little surprised we don't run the command from the project directory on Linux.

@joerick
Copy link
Contributor

joerick commented Sep 15, 2025

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 {project} placeholder.

@arcondello
Copy link
Author

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 {project} placeholder.

Sure, I can do that

@arcondello
Copy link
Author

arcondello commented Sep 16, 2025

As an alternative, if the intent is always to run the repair-wheel-command in the project directory, I can change the PR to update the documentation to specify that. IMO the explicit approach gives more flexibility in the future, but I am happy either way.

@joerick
Copy link
Contributor

joerick commented Sep 20, 2025

As an alternative, if the intent is always to run the repair-wheel-command in the project directory, I can change the PR to update the documentation to specify that.

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 {package} to be expanded in repair-wheel-command as well. If you have time :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider making {project} placeholder available to repair-wheel-command CIBW_REPAIR_WHEEL_COMMAND does not expand {project} (and other placeholders)
4 participants