-
Notifications
You must be signed in to change notification settings - Fork 807
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
Running setup.py
as a script and its use as a CLI tool are deprecated
#2208
Comments
@zooba Given you added the ARM64 cross-compilation CI job. Any idea how to migrate this command to not call pywin32/.github/workflows/main.yml Lines 91 to 96 in c6acaf5
|
setuptools supports inserting an additional configuration file through environment variables, you can see how cibuildwheel sets up cross-compiling here: https://github.com/pypa/cibuildwheel/blob/main/cibuildwheel/windows.py#L141 |
Thanks! I think yesterday I finally figured out how to use GitHub's ARM-based Windows runners should be freely publicly available by the end of the year anyway, so whatever works for now.
https://github.com/orgs/community/discussions/19197#discussioncomment-10895290
Update: |
Yeah, cross-compiling is nice if you want to do all the builds in a single job and then run tests on the target machines, but it's optional. Really the only difference is that setuptools assumes you're targeting the current platform (and only recently gained the ability to detect Windows ARM64 properly). |
https://packaging.python.org/en/latest/discussions/setup-py-deprecated/#is-setup-py-deprecated
https://setuptools.pypa.io/en/latest/deprecated/commands.html#running-setuptools-commands
pywin32 itself should move away from it, I have yet to investigate everything needed for pywin32 to move away from it.
Relates to #2119
To stop using
python setup.py
, the--skip-verstamp
flag needs to be changed. Either trying to pass it through:Being able to build / install from
pip install
will open the door to:pywin32/pyrightconfig.json
Lines 45 to 51 in 9ef5061
The text was updated successfully, but these errors were encountered: