Skip to content
This repository was archived by the owner on Feb 14, 2023. It is now read-only.

Python 3.5 for 0.22.X #49

Merged
merged 2 commits into from
Mar 4, 2020
Merged

Conversation

jeremiedbb
Copy link
Contributor

Python 3.5 was removed from the matrix during the move to azure pipelines but 0.22.X still support py35.

@jeremiedbb
Copy link
Contributor Author

jeremiedbb commented Mar 4, 2020

I guess we can just fetch the py35 artifacts and upload them to pypi.

However we need to revert back right after since this ci is also used for the nightly builds and the dev version dropped support for py35

@adrinjalali
Copy link
Collaborator

yeah, not clean. We really need a better release process. @thomasjpfan help us lolol (azure pipelines? :D :P)

@@ -75,6 +87,9 @@ jobs:
name: macOS
vmImage: xcode9-macos10.13
matrix:
py_3.5_64:
MB_PYTHON_VERSION: "3.5"
NP_BUILD_DEP: "numpy==1.13.3"
Copy link
Contributor

@ogrisel ogrisel Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not 1.12.1 as for Windows?

We should try to use the even older numpy 1.11.0 for building as noted below.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They were different for py36, I just used the same as py36 for each platform.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also consistent with https://pypi.org/project/oldest-supported-numpy/ BTW

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes for macos, but not for windows. And we don't force the version for linux. I don't know why

MB_PYTHON_VERSION: "3.5"
PLAT: "i686"
py_3.5_64:
MB_PYTHON_VERSION: "3.5"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should force the build against the oldest supported of numpy for Python 3.5.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but the existing ones are not following oldest supported numpy. I thought that was intentional

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably because I used the version numbers for 0.23 and not 0.22.X

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anyway that should be fine as it is.

@ogrisel
Copy link
Contributor

ogrisel commented Mar 4, 2020

yeah, not clean. We really need a better release process. @thomasjpfan help us lolol (azure pipelines? :D :P)

This is already Azure Pipelines. Actually it's my fault when we recently migrated to Azure Pipelines I removed older versions of Python to speed things up but I forgot that we still needed Python 3.5 for the 0.22.X branch.

@ogrisel
Copy link
Contributor

ogrisel commented Mar 4, 2020

In the old travis config we used to build the Python 3.5 wheels against numpy 1.11.0:

https://github.com/MacPython/scikit-learn-wheels/pull/46/files#diff-6f5779d3f3cbf5c00bd0bade61862c0d

@ogrisel
Copy link
Contributor

ogrisel commented Mar 4, 2020

Note that for 0.23 and following, we should try to find a way to automatically fetch the oldest supported version of numpy and scipy from the pyproject.toml file, crossed with the oldest available wheel files on pypi.org for each Python version: even if scikit-learn 0.23 in general should work with numpy>=1.13.3 in general, numpy 1.13.3 would be available as wheels only for Python versions that existed when numpy 1.13.3 was released.

Copy link
Contributor

@ogrisel ogrisel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@ogrisel ogrisel merged commit 029c445 into MacPython:master Mar 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants