Skip to content

Replace setup.py bdist_wheel with python -m build --wheel#156712

Closed
zklaus wants to merge 34 commits intogh/zklaus/11/basefrom
gh/zklaus/11/head
Closed

Replace setup.py bdist_wheel with python -m build --wheel#156712
zklaus wants to merge 34 commits intogh/zklaus/11/basefrom
gh/zklaus/11/head

Conversation

@zklaus
Copy link
Copy Markdown
Collaborator

@zklaus zklaus commented Jun 24, 2025

Previously we already replaced most use of python setup.py develop/install.

This PR also replaces the use of setup.py bdist_wheel with the modern python -m build --wheel alternative.

Stack from ghstack (oldest at bottom):

[ghstack-poisoned]
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot bot commented Jun 24, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/156712

Note: Links to docs will display an error until the docs builds have been completed.

❌ 7 New Failures

As of commit 517410c with merge base e64dd8c (image):

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[ghstack-poisoned]
zklaus added a commit to zklaus/pytorch that referenced this pull request Jun 25, 2025
zklaus added 3 commits August 11, 2025 13:00
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
zklaus added 2 commits August 11, 2025 18:18
[ghstack-poisoned]
[ghstack-poisoned]
@atalman atalman added the ciflow/binaries Trigger all binary build and upload jobs on the PR label Aug 12, 2025
@atalman
Copy link
Copy Markdown
Contributor

atalman commented Aug 12, 2025

@zklaus one way of approaching this is to break it into parts: Linux, MacOS and Windows. We also need to test binary builds with these changes, attached ciflow/binaries

[ghstack-poisoned]
@zklaus zklaus mentioned this pull request Sep 2, 2025
[ghstack-poisoned]
@atalman atalman added this to the 2.10.0 milestone Sep 2, 2025
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
zklaus added a commit that referenced this pull request Sep 8, 2025
[ghstack-poisoned]
zklaus added a commit that referenced this pull request Sep 28, 2025
[ghstack-poisoned]
zklaus added a commit that referenced this pull request Sep 29, 2025
[ghstack-poisoned]
zklaus added a commit that referenced this pull request Sep 29, 2025
[ghstack-poisoned]
zklaus added a commit that referenced this pull request Sep 29, 2025
@zklaus
Copy link
Copy Markdown
Collaborator Author

zklaus commented Sep 29, 2025

@pytorchbot merge -i

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@zklaus
Copy link
Copy Markdown
Collaborator Author

zklaus commented Sep 29, 2025

@pytorchbot merge

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@zklaus
Copy link
Copy Markdown
Collaborator Author

zklaus commented Sep 29, 2025

@pytorchbot merge -f "The rocm 7 test failures are unrelated."

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@github-actions github-actions bot deleted the gh/zklaus/11/head branch October 30, 2025 02:17
pytorchmergebot pushed a commit that referenced this pull request Nov 6, 2025
…ion (#166848)

Fixes #166326

The PR fixes the following error:
```
python -m build: error: unrecognized arguments: --no-build-isolation
```

The regression has been introduced in the [commit](50d418f#diff-e5a6ba9ea3717e5913cd885e81f143937ea727282edd6939479a2a60b1051bf5R73) in the scope of [PR](#156712).

Pull Request resolved: #166848
Approved by: https://github.com/seemethere
yarongmu-google pushed a commit to yarongmu-google/pytorch that referenced this pull request Nov 7, 2025
…ion (pytorch#166848)

Fixes pytorch#166326

The PR fixes the following error:
```
python -m build: error: unrecognized arguments: --no-build-isolation
```

The regression has been introduced in the [commit](pytorch@50d418f#diff-e5a6ba9ea3717e5913cd885e81f143937ea727282edd6939479a2a60b1051bf5R73) in the scope of [PR](pytorch#156712).

Pull Request resolved: pytorch#166848
Approved by: https://github.com/seemethere
Silv3S pushed a commit to Silv3S/pytorch that referenced this pull request Nov 18, 2025
…ion (pytorch#166848)

Fixes pytorch#166326

The PR fixes the following error:
```
python -m build: error: unrecognized arguments: --no-build-isolation
```

The regression has been introduced in the [commit](pytorch@50d418f#diff-e5a6ba9ea3717e5913cd885e81f143937ea727282edd6939479a2a60b1051bf5R73) in the scope of [PR](pytorch#156712).

Pull Request resolved: pytorch#166848
Approved by: https://github.com/seemethere
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/binaries Trigger all binary build and upload jobs on the PR ciflow/trunk Trigger trunk jobs on your pull request Merged open source release notes: releng release notes category suppress-bc-linter Suppresses the failures of API backward-compatibility linter (Lint/bc_linter)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants