-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
BLD Build 3.10 wheel [cd build gh] #21232
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
Conversation
pyproject.toml
Outdated
@@ -3,7 +3,7 @@ | |||
requires = [ | |||
"setuptools", | |||
"wheel", | |||
"Cython>=0.28.5", | |||
"Cython>=0.28.5,<3.0", |
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.
Needed this to stop Cython 3.0 from installing with PIP_PRE=true
PIP_PRE=true
is required because scipy 3.10 is only avaliable as a dev release in https://pypi.anaconda.org/scipy-wheels-nightly/simple
.github/workflows/wheels.yml
Outdated
# Comment out when numpy/scipy dependencies are on pypi | ||
- name: Set pypi index for python dev | ||
if: matrix.python == 310 | ||
run: | | ||
echo "EXTRA_CIBW_ENVIRONMENT=PIP_EXTRA_INDEX_URL=https://pypi.anaconda.org/scipy-wheels-nightly/simple PIP_PRE=true" >> $GITHUB_ENV | ||
|
||
# Do not use the dev version of pandas | ||
echo "PANDAS_VERSION_SPECIFIER=<1.4" >> $GITHUB_ENV |
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.
When a new version of Python come up, I expect the builds for the Python RC to be in https://pypi.anaconda.org/scipy-wheels-nightly/simple first, so setting PIP_PRE=true
is required to automatically get the dev builds.
Currently there is a mix of Python 3.10 wheels on scipy-wheels-nightly
and on pypi. numpy and pandas is on pypi and scipy is on scipy-wheels-nightly
.
Marked for 1.0.1 so we can have Python 3.10 builds for |
@@ -7,6 +7,7 @@ COMMIT_MSG=$(git log --no-merges -1 --oneline) | |||
|
|||
# The commit marker "[cd build]" will trigger the build when required | |||
if [[ "$GITHUB_EVENT_NAME" == schedule || | |||
"$COMMIT_MSG" =~ \[cd\ build\] ]]; then | |||
"$COMMIT_MSG" =~ \[cd\ build\] || | |||
"$COMMIT_MSG" =~ \[cd\ build\ gh\] ]]; then |
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.
nice :)
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.
do we have this documented?
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.
now we do (as part of #21849).
It nice to see that it works but shouldn't we wait for numpy and scipy to be release for Python 3.10 before merging this with a simpler config that does not rely on the dev wheels? |
I agree. I'll place this PR into draft mode and take it out of draft when numpy/scipy wheels are on pypi. |
Still waiting on MacPython/scipy-wheels#132 |
SciPy on Windows & Python 3.10 is now fixed on PyPi. This PR should be good to go. |
Hi! Thanks to the |
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 @thomasjpfan
@@ -7,6 +7,7 @@ COMMIT_MSG=$(git log --no-merges -1 --oneline) | |||
|
|||
# The commit marker "[cd build]" will trigger the build when required | |||
if [[ "$GITHUB_EVENT_NAME" == schedule || | |||
"$COMMIT_MSG" =~ \[cd\ build\] ]]; then | |||
"$COMMIT_MSG" =~ \[cd\ build\] || | |||
"$COMMIT_MSG" =~ \[cd\ build\ gh\] ]]; then |
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.
do we have this documented?
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.
LGTM once the remaining review comments are dealt with. Thanks very much @thomasjpfan!
Once merged, will need to backport this to the 1.0.X branch. From there we could either build some Python 3.10 wheels for 1.0.1 and upload them manually to pypi or we could wait for 1.0.2 which should happen soon-ish. |
Thanks @ogrisel and @thomasjpfan ! |
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.
LGTM assuming CI stays green after the merge conflicts resolution. If #21827 is merged first we will need to add the Python 3.10 entry to macos/arm64
here before merging.
The unrelated Azure Pipelines failures on Windows has already been reported here: #21798. |
Nice. |
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
Fixes #21401
Now that 3.10 wheels for numpy and scipy are in https://pypi.anaconda.org/scipy-wheels-nightly/simple, this PR enables us to build scikit-learn wheels with them.
Note that
numpy
andscipy
is onmanylinux2014
.