-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
refactor wheel builder to use workflows and download/build separately #5412
Conversation
- {VERSION: "3.6", MSVC_VERSION: "2019"} | ||
- {VERSION: "3.7", MSVC_VERSION: "2019"} | ||
- {VERSION: "3.8", MSVC_VERSION: "2019"} | ||
- {VERSION: "3.8", MSVC_VERSION: "2019", "USE_ABI3": "true", "ABI_VERSION": "cp36"} |
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.
I win the fight on bcrypt but lose it here?
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.
You lose it here for now. I don't want to have our wheel infra only capable of building the new style when we don't know the results of that experiment. If bcrypt goes well we can update this before 3.1 release.
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.
I have confidence in the bcrypt expirement, so I guess I'm ok waiting a month to delete it :-)
Co-authored-by: Alex Gaynor <alex.gaynor@gmail.com>
This fixes #4907 |
Build succeeded (check pipeline).
|
This one retains the abi3/non-abi3 windows hack just in case we release before our bcrypt experiment has conclusive results.